use flannel and add-on kube-dns， but kube-dns don't work about dns

[Blfrg]

I recently resolved the same issue, however I use canal (calico+flannel) on standard kubernetes hyperkube (no kubeadm) on CoreOS (Container Linux). This is likely a k8s/flannel issue and not a kube-dns issue.

Flannel is in the process of merging with calico (combined = canal), so I recommend checking it out if possible for your environment. Canal has a kubeadm specific install and additional info on the calico site. This is more simplified than the original flannel instructions, and is now fully instantiated from within kubernetes itself (no having to tweak docker).

Note the different 1.5 and 1.6 install guides and files. Don't forget to update the iface in your case.

For my resolution (self/standard hosted install), I upgraded the canal images to their latest whole versions found on quay.io/organization/calico. The kubeadm specific install appears to use the latest image versions already with the exception of calico/node:v1.1.0 => v1.1.1 (though it may not be necessary to update it).

I hope that helps or leads you to more helpful information.

[wadee]

@Blfrg appreciate your reply,I will try it out soon！！

[cmluciano]

@wadee Can you please post the details on how you install flannel? Did you grab the latest from master?

[wadee]

@cmluciano sorry for replying so late ……

kubectl create -f kube-flannel-rbac.yml
kubectl create --namespace kube-system -f kube-flannel.yml

• specially node use wifi for connected, so i modify the kube-flannel.yml configure params as below：
  image: quay.io/coreos/flannel:v0.7.0-arm
  command: [ "/opt/bin/flanneld", "--ip-masq", "--kube-subnet-mgr", "--iface=wlan0"]

i am sure that flannel:v0.7.0-arm is the latest flannel for the arm-system at that time.

and here is the whole content of the kube-flannel.yml :

---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: flannel
  namespace: kube-system
---
kind: ConfigMap
apiVersion: v1
metadata:
  name: kube-flannel-cfg
  namespace: kube-system
  labels:
    tier: node
    app: flannel
data:
  cni-conf.json: |
    {
      "name": "cbr0",
      "type": "flannel",
      "delegate": {
        "isDefaultGateway": true
      }
    }
  net-conf.json: |
    {
      "Network": "10.244.0.0/16",
      "Backend": {
        "Type": "vxlan"
      }
    }
---
apiVersion: extensions/v1beta1
kind: DaemonSet
metadata:
  name: kube-flannel-ds
  namespace: kube-system
  labels:
    tier: node
    app: flannel
spec:
  template:
    metadata:
      labels:
        tier: node
        app: flannel
    spec:
      hostNetwork: true
      nodeSelector:
        beta.kubernetes.io/arch: arm
      tolerations:
      - key: node-role.kubernetes.io/master
        operator: Exists
        effect: NoSchedule
      serviceAccountName: flannel
      containers:
      - name: kube-flannel
        image: quay.io/coreos/flannel:v0.7.0-arm
        command: [ "/opt/bin/flanneld", "--ip-masq", "--kube-subnet-mgr", "--iface=wlan0"]
        securityContext:
          privileged: true
        env:
        - name: POD_NAME
          valueFrom:
            fieldRef:
              fieldPath: metadata.name
        - name: POD_NAMESPACE
          valueFrom:
            fieldRef:
              fieldPath: metadata.namespace
        volumeMounts:
        - name: run
          mountPath: /run
        - name: flannel-cfg
          mountPath: /etc/kube-flannel/
      - name: install-cni
        image: quay.io/coreos/flannel:v0.7.0-arm
        command: [ "/bin/sh", "-c", "set -e -x; cp -f /etc/kube-flannel/cni-conf.json /etc/cni/net.d/10-flannel.conf; while true; do sleep 3600; done" ]
        volumeMounts:
        - name: cni
          mountPath: /etc/cni/net.d
        - name: flannel-cfg
          mountPath: /etc/kube-flannel/
      volumes:
        - name: run
          hostPath:
            path: /run
        - name: cni
          hostPath:
            path: /etc/cni/net.d
        - name: flannel-cfg
          configMap:
            name: kube-flannel-cfg

[cmluciano]

Your deployment seems similar to flannel's latest example, with the exception of the arm platform reference and a custom iface.

Can you retry with the v0.7.1-arm image?

I agree that this issue might be better served in the flannel repository.

[k8s-ci-robot]

@cmluciano: These labels do not exist in this repository: sig/network.

In response to this:

/sig network

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[cmluciano]

/assign

[wadee]

yeah, I agree with u.
I will try the latest v0.7.1-arm image and I will create the same issue to the flannel repository.
so I decide to close the issue.
thx to all guys!