[Release-1.27] - Add flannel as CNI plugin

[manuelbuil]

Backport fix for Add flannel as CNI plugin

• Add flannel as CNI plugin #5215

[fmoral2]

Validated on Version:

-$   v1.27.11+rke2r1 

 

Environment Details

Infrastructure
Cloud EC2 instance

Node(s) CPU architecture, OS, and Version:
SUSE Linux Enterprise Server 15 SP4

Cluster Configuration:
1 server node
1 agent
1 windows

Steps to validate the fix

1. Install rke2 with cni: flannel
2. Validate it works as expected in windowns and linux

Reproduction Issue:

Validation Results:

      
 
 PASSED! Test: Mixed OS Cluster Starts Up with no issues
09:24:17.145  �[38;5;10m•�[0m
09:24:17.145  
09:24:17.145  Cluster nodes:
09:24:17.145  ip-0.us-east-2.compute.internal   Ready   control-plane,etcd,master   6m3s   v1.27.11+rke2r1      Ubuntu 22.04.1 LTS               5.15.0-1019-aws   containerd://1.7.11-k3s2
09:24:17.145  ip-0.us-east-2.compute.internal   Ready   <none>                      4m     v1.27.11+rke2r1       <none>         Ubuntu 22.04.1 LTS               5.15.0-1019-aws   containerd://1.7.11-k3s2
09:24:17.145  ip-ac1f2610                                  Ready   <none>                      10s    v1.27.11             Windows Server 2022 Datacenter   10.0.20348.350    containerd://1.7.11-k3s2
09:24:17.145  
09:24:17.145  
09:24:17.145  PASSED! Test: Mixed OS Cluster Validates Node
09:24:17.145  �[38;5;10m•�[0m
09:24:17.145  Cluster pods:
09:24:17.145   kube-system   cloud-controller-manager-ip-0.us-east-2.compute.internal   1/1   Running     0              5m6s     ip-0.us-east-2.compute.internal   <none>   <none>
09:24:17.145  kube-system   etcd-ip-0.us-east-2.compute.internal                       1/1   Running     0              5m1s       ip-0.us-east-2.compute.internal   <none>   <none>
09:24:17.145  kube-system   helm-install-rke2-coredns-gjh8h                                       0/1   Completed   0              5m47s   0   ip-0.us-east-2.compute.internal   <none>   <none>
09:24:17.145  kube-system   helm-install-rke2-flannel-dkrd6                                       0/1   Completed   0              5m47s   0   ip-0.us-east-2.compute.internal   <none>   <none>
09:24:17.145  kube-system   helm-install-rke2-ingress-nginx-6vn5v                                 0/1   Completed   0              5m47s   10.42.0.6      ip-0.us-east-2.compute.internal   <none>   <none>
09:24:17.146  kube-system   helm-install-rke2-metrics-server-nwnxn                                0/1   Completed   0              5m47s   10.42.0.4      ip-0.us-east-2.compute.internal   <none>   <none>
09:24:17.146  kube-system   helm-install-rke2-snapshot-controller-8d8rc                           0/1   Completed   1              5m47s   10.42.0.3      ip-0.us-east-2.compute.internal   <none>   <none>
09:24:17.146  kube-system   helm-install-rke2-snapshot-controller-crd-cp62l                       0/1   Completed   0              5m47s   10.42.0.2      ip-0.us-east-2.compute.internal   <none>   <none>
09:24:17.146  kube-system   helm-install-rke2-snapshot-validation-webhook-78qm7                   0/1   Completed   0              5m47s   10.42.0.5      ip-0.us-east-2.compute.internal   <none>   <none>
09:24:17.146  kube-system   kube-apiserver-ip-0.us-east-2.compute.internal             1/1   Running     0              5m23s   0   ip-0.us-east-2.compute.internal   <none>   <none>
09:24:17.146  kube-system   kube-controller-manager-ip-0.us-east-2.compute.internal    1/1   Running     0              5m3s    0   ip-0.us-east-2.compute.internal   <none>   <none>
09:24:17.146  kube-system   kube-flannel-ds-kmrmk                                                 1/1   Running     0              5m28s   0   ip-0.us-east-2.compute.internal   <none>   <none>
09:24:17.146  kube-system   kube-flannel-ds-njrl7                                                 1/1   Running     1 (3m8s ago)   4m1s    04.109   ip-0.us-east-2.compute.internal   <none>   <none>
09:24:17.146  kube-system   kube-proxy-ip-0.us-east-2.compute.internal                 1/1   Running     0              4m56s   0   ip-0.us-east-2.compute.internal   <none>   <none>
09:24:17.146  kube-system   kube-proxy-ip-0.us-east-2.compute.internal                 1/1   Running     0              4m1s    04.109   ip-0.us-east-2.compute.internal   <none>   <none>
09:24:17.146  kube-system   kube-scheduler-ip-0.us-east-2.compute.internal             1/1   Running     0              4m59s   0   ip-0.us-east-2.compute.internal   <none>   <none>
09:24:17.146  kube-system   rke2-coredns-656fdfd5cb-gflvz                                         1/1   Running     0              5m27s   10.42.0.7      ip-0.us-east-2.compute.internal   <none>   <none>
09:24:17.146  kube-system   rke2-coredns-656fdfd5cb-js26b                                         1/1   Running     0              4m      10.42.1.3      ip-0.us-east-2.compute.internal   <none>   <none>
09:24:17.146  kube-system   rke2-coredns-autoscaler-7fff9bd6d6-r68nx                              1/1   Running     0              5m27s   10.42.0.8      ip-0.us-east-2.compute.internal   <none>   <none>
09:24:17.146  kube-system   rke2-ingress-nginx-controller-6n69v                                   1/1   Running     0              4m31s   10.42.0.13     ip-0.us-east-2.compute.internal   <none>   <none>
09:24:17.146  kube-system   rke2-ingress-nginx-controller-qplc2                                   1/1   Running     0              3m40s   10.42.1.2      ip-0.us-east-2.compute.internal   <none>   <none>
09:24:17.147  kube-system   rke2-metrics-server-5c9768ff67-ngthz                                  1/1   Running     0              4m49s   10.42.0.9      ip-0.us-east-2.compute.internal   <none>   <none>
09:24:17.147  kube-system   rke2-snapshot-controller-7d6476d7cb-n9kwn                             1/1   Running     0              4m46s   10.42.0.10     ip-0.us-east-2.compute.internal   <none>   <none>
09:24:17.147  kube-system   rke2-snapshot-validation-webhook-5649fbd66c-jdddz                     1/1   Running     0              4m45s   10.42.0.11     ip-0.us-east-2.compute.internal   <none>   <none>
09:24:17.147  
09:24:17.147  
09:24:17.147  PASSED! Test: Mixed OS Cluster Validate Pods
09:24:17.147  �[38;5;10m•�[0m
09:24:17.147  Applying  pod_client.yaml
09:24:17.147  
09:24:17.147  Applying  windows_app_deployment.yaml
09:24:18.576  �[36mINFO�[0m[2024-02-16T12:24:18Z] Extracted from local kube config file server ip: 3.14.141.119 
09:24:18.576  �[36mINFO�[0m[2024-02-16T12:24:18Z] Extracted from local kube config file server ip: 3.14.141.119 
09:24:18.833  
09:24:18.833  Connecting to services
09:27:11.242  
09:27:11.242  Removing pod_client.yaml
09:27:12.834  
09:27:12.834  Removing windows_app_deployment.yaml
09:27:16.231  
09:27:16.231  PASSED! Test: Mixed OS Cluster Validates internode connectivity over the vxlan tunnel
09:28:38.528  �[38;5;10m•�[0m
09:28:38.528  PASSED! Test: Mixed OS Cluster Validates cluster by running sonobuoy mixed OS plugin
09:28:38.528  �[38;5;10m•�[0m
09:28:38.528  
09:28:38.528  �[38;5;10m�[1mRan 5 of 5 Specs in 796.000 seconds�[0m
09:28:38.528  �[38;5;10m�[1mSUCCESS!�[0m -- �[38;5;10m�[1m5 Passed�[0m | �[38;5;9m�[1m0 Failed�[0m | �[38;5;11m�[1m0 Pending�[0m | �[38;5;14m�[1m0 Skipped�[0m
09:28:38.528  --- PASS: TestMixedOSClusterCreateSuite (796.00s)
09:28:38.528  PASS
09:28:38.528  ok  	github.com/rancher/distros-test-framework/entrypoint/mixedoscluster	796.127s