kiranchavala commented on issue #6637: URL: https://github.com/apache/cloudstack/issues/6637#issuecomment-1943228696
@weizhouapache @rohityadavcloud @jkacou I have tested with Calico CNI the k8s cluster creation working fine. https://docs.tigera.io/calico/latest/about/ https://github.com/projectcalico/calico/blob/master/manifests/calico.yaml ---- With Flannel CNI the cluster creation was failing 1. Execute the create-kubernetes-binaries-iso.sh script wih the following parametes ./create-kubernetes-binaries-iso.sh ./ 1.29.1 1.2.0 1.26.0 https://raw.githubusercontent.com/flannel-io/flannel/master/Documentation/kube-flannel.yml https://raw.githubusercontent.com/kubernetes/dashboard/v2.7.0/aio/deploy/recommended.yaml setup-1.29.1 2. Register the Kunbernetes ISO 3. Lanch a k8s cluster 4. The cluster fails to come up ``` root@k2-control-18d9bbfe065:/opt/cloud/bin# kubectl logs -n kube-flannel -f kube-flannel-ds-zxv85 Defaulted container "kube-flannel" out of: kube-flannel, install-cni-plugin (init), install-cni (init) I0212 05:50:47.071491 1 main.go:209] CLI flags config: {etcdEndpoints:http://127.0.0.1:4001,http://127.0.0.1:2379 etcdPrefix:/coreos.com/network etcdKeyfile: etcdCertfile: etcdCAFile: etcdUsername: etcdPassword: version:false kubeSubnetMgr:true kubeApiUrl: kubeAnnotationPrefix:flannel.alpha.coreos.com kubeConfigFile: iface:[] ifaceRegex:[] ipMasq:true ifaceCanReach: subnetFile:/run/flannel/subnet.env publicIP: publicIPv6: subnetLeaseRenewMargin:60 healthzIP:0.0.0.0 healthzPort:0 iptablesResyncSeconds:5 iptablesForwardRules:true netConfPath:/etc/kube-flannel/net-conf.json setNodeNetworkUnavailable:true} W0212 05:50:47.071870 1 client_config.go:617] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work. I0212 05:50:47.111138 1 kube.go:139] Waiting 10m0s for node controller to sync I0212 05:50:47.111565 1 kube.go:461] Starting kube subnet manager I0212 05:50:48.112838 1 kube.go:146] Node controller sync successful I0212 05:50:48.113029 1 main.go:229] Created subnet manager: Kubernetes Subnet Manager - k2-node-18d9bc019c5 I0212 05:50:48.113056 1 main.go:232] Installing signal handlers I0212 05:50:48.114338 1 main.go:540] Found network config - Backend type: vxlan I0212 05:50:48.114574 1 match.go:210] Determining IP address of default interface I0212 05:50:48.117010 1 match.go:263] Using interface with name eth0 and address 10.1.1.8 I0212 05:50:48.117128 1 match.go:285] Defaulting external address to interface address (10.1.1.8) I0212 05:50:48.117695 1 vxlan.go:141] VXLAN config: VNI=1 Port=0 GBP=false Learning=false DirectRouting=false I0212 05:50:48.124242 1 kube.go:621] List of node(k2-node-18d9bc019c5) annotations: map[string]string{"kubeadm.alpha.kubernetes.io/cri-socket":"unix:///var/run/containerd/containerd.sock", "node.alpha.kubernetes.io/ttl":"0", "volumes.kubernetes.io/controller-managed-attach-detach":"true"} E0212 05:50:48.127081 1 main.go:332] Error registering network: failed to acquire lease: node "k2-node-18d9bc019c5" pod cidr not assigned I0212 05:50:48.127652 1 main.go:520] Stopping shutdownHandler.. ``` It would be ideal if we could provide the option of selecting the CNI during the CKS Cluster creation -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
