hmm, that manifest seems to not be correct, it had to be updated in order to work with 1.16, it has
apiVersion: extensions/v1beta1 kind: DaemonSet
and that apiVersion is no longer served since 1.16
DaemonSet, Deployment, and ReplicaSet resources will no longer be served from extensions/v1beta1, apps/v1beta1, or apps/v1beta2 by default in v1.16. Migrate to the apps/v1 API, available since v1.9. Existing persisted data can be retrieved/updated via the apps/v1 API.
https://groups.google.com/d/msg/kubernetes-dev/je0rjyfTVyc/gEUw1YcyAQAJ On Wed, 17 Jul 2019 at 20:06, Thorsten Kukuk <kukuk@suse.de> wrote:
Hi,
On Wed, Jul 17, Robert Munteanu wrote:
- kubeadm init --pod-network-cidr=10.244.0.0/16 on master - set up ~/.kube/config on master - kubectl apply -f /usr/share/k8s-yaml/flannel/kube-flannel.yaml on master - kubeadm join on worker-1
I noticed that DNS resolution does not work for cluster-local services, which is quite problematic.
I have the feeling, that the cni initialization of our flannel image or manifest doesn't work correct. You could try: kubectl delete -f /usr/share/k8s-yaml/flannel/kube-flannel.yaml kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-f...
Thorsten
-- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendoerffer, Mary Higgins, Sri Rasiah, HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-kubic+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kubic+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-kubic+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kubic+owner@opensuse.org