[Release-1.26] - 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.26.14+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
10:35:12.834  �[38;5;10m•�[0m
10:35:12.834  
10:35:12.834  Cluster nodes:
10:35:12.834  ip-0.us-east-2.compute.internal   Ready   <none>                      4m8s    v1.26.14+rke2r1  0  <none>          Ubuntu 22.04.1 LTS               5.15.0-1019-aws   containerd://1.7.11-k3s2
10:35:12.835  ip-172-31-7-226.us-east-2.compute.internal    Ready   control-plane,etcd,master   7m18s   v1.26.14+rke2r1  0    Ubuntu 22.04.1 LTS               5.15.0-1019-aws   containerd://1.7.11-k3s2
10:35:12.835  ip-ac1f2610                                   Ready   <none>                      11s     v1.26.14             Windows Server 2022 Datacenter   10.0.20348.350    containerd://1.7.11-k3s2
10:35:12.835  
10:35:12.835  
10:35:12.835  PASSED! Test: Mixed OS Cluster Validates Node
10:35:12.835  �[38;5;10m•�[0m
10:35:12.835  Cluster pods:
10:35:12.835   kube-system   cloud-controller-manager-ip-172-31-7-226.us-east-2.compute.internal   1/1   Running     0     7m14s  0    ip-172-31-7-226.us-east-2.compute.internal    <none>   <none>
10:35:12.835  kube-system   etcd-ip-172-31-7-226.us-east-2.compute.internal                       1/1   Running     0     6m47s  0    ip-172-31-7-226.us-east-2.compute.internal    <none>   <none>
10:35:12.835  kube-system   helm-install-rke2-coredns-ncgh4                                       0/1   Completed   0     6m59s  0    ip-172-31-7-226.us-east-2.compute.internal    <none>   <none>
10:35:12.835  kube-system   helm-install-rke2-flannel-ww4hb                                       0/1   Completed   0     6m59s  0    ip-172-31-7-226.us-east-2.compute.internal    <none>   <none>
10:35:12.835  kube-system   helm-install-rke2-ingress-nginx-mgtf9                                 0/1   Completed   0     6m59s   10.42.0.6       ip-172-31-7-226.us-east-2.compute.internal    <none>   <none>
10:35:12.835  kube-system   helm-install-rke2-metrics-server-v8zrc                                0/1   Completed   0     6m59s   10.42.0.7       ip-172-31-7-226.us-east-2.compute.internal    <none>   <none>
10:35:12.835  kube-system   helm-install-rke2-snapshot-controller-crd-vmq6p                       0/1   Completed   0     6m59s   10.42.0.3       ip-172-31-7-226.us-east-2.compute.internal    <none>   <none>
10:35:12.835  kube-system   helm-install-rke2-snapshot-controller-htjnl                           0/1   Completed   1     6m59s   10.42.0.5       ip-172-31-7-226.us-east-2.compute.internal    <none>   <none>
10:35:12.835  kube-system   helm-install-rke2-snapshot-validation-webhook-446x5                   0/1   Completed   0     6m59s   10.42.0.2       ip-172-31-7-226.us-east-2.compute.internal    <none>   <none>
10:35:12.835  kube-system   kube-apiserver-ip-172-31-7-226.us-east-2.compute.internal             1/1   Running     0     7m11s  0    ip-172-31-7-226.us-east-2.compute.internal    <none>   <none>
10:35:12.835  kube-system   kube-controller-manager-ip-172-31-7-226.us-east-2.compute.internal    1/1   Running     0     7m16s  0    ip-172-31-7-226.us-east-2.compute.internal    <none>   <none>
10:35:12.835  kube-system   kube-flannel-ds-kpbxb                                                 1/1   Running     0     4m9s   0  ip-0.us-east-2.compute.internal   <none>   <none>
10:35:12.835  kube-system   kube-flannel-ds-mz4db                                                 1/1   Running     0     6m49s  0    ip-172-31-7-226.us-east-2.compute.internal    <none>   <none>
10:35:12.835  kube-system   kube-proxy-ip-0.us-east-2.compute.internal                1/1   Running     0     4m8s   0  ip-0.us-east-2.compute.internal   <none>   <none>
10:35:12.835  kube-system   kube-proxy-ip-172-31-7-226.us-east-2.compute.internal                 1/1   Running     0     7m9s   0    ip-172-31-7-226.us-east-2.compute.internal    <none>   <none>
10:35:12.835  kube-system   kube-scheduler-ip-172-31-7-226.us-east-2.compute.internal             1/1   Running     0     7m16s  0    ip-172-31-7-226.us-east-2.compute.internal    <none>   <none>
10:35:12.835  kube-system   rke2-coredns-64f789b976-2dvlk                                         1/1   Running     0     6m48s   10.42.0.4       ip-172-31-7-226.us-east-2.compute.internal    <none>   <none>
10:35:12.835  kube-system   rke2-coredns-64f789b976-xlc6q                                         1/1   Running     0     4m3s    10.42.1.2       ip-0.us-east-2.compute.internal   <none>   <none>
10:35:12.835  kube-system   rke2-coredns-autoscaler-689598f748-qnbfm                              1/1   Running     0     6m48s   10.42.0.8       ip-172-31-7-226.us-east-2.compute.internal    <none>   <none>
10:35:12.835  kube-system   rke2-ingress-nginx-controller-nvmt8                                   1/1   Running     0     2m33s   10.42.1.3       ip-0.us-east-2.compute.internal   <none>   <none>
10:35:12.835  kube-system   rke2-ingress-nginx-controller-r7v5s                                   1/1   Running     0     5m50s   10.42.0.13      ip-172-31-7-226.us-east-2.compute.internal    <none>   <none>
10:35:12.836  kube-system   rke2-metrics-server-84b8d89697-64fzs                                  1/1   Running     0     6m8s    10.42.0.10      ip-172-31-7-226.us-east-2.compute.internal    <none>   <none>
10:35:12.836  kube-system   rke2-snapshot-controller-6f7bbb497d-4n4r6                             1/1   Running     0     6m4s    10.42.0.12      ip-172-31-7-226.us-east-2.compute.internal    <none>   <none>
10:35:12.836  kube-system   rke2-snapshot-validation-webhook-65b5675d5c-m6skc                     1/1   Running     0     6m8s    10.42.0.9       ip-172-31-7-226.us-east-2.compute.internal    <none>   <none>
10:35:12.836  
10:35:12.836  
10:35:12.836  PASSED! Test: Mixed OS Cluster Validate Pods
10:35:12.836  �[38;5;10m•�[0m
10:35:12.836  Applying  pod_client.yaml
10:35:13.435  
10:35:13.435  Applying  windows_app_deployment.yaml
10:35:15.458  �[36mINFO�[0m[2024-02-16T13:35:15Z] Extracted from local kube config file server ip: 3.145.41.216 
10:35:15.459  �[36mINFO�[0m[2024-02-16T13:35:15Z] Extracted from local kube config file server ip: 3.145.41.216 
10:35:15.715  
10:35:15.715  Connecting to services
10:38:08.148  
10:38:08.148  Removing pod_client.yaml
10:38:10.334  
10:38:10.334  Removing windows_app_deployment.yaml
10:38:13.934  
10:38:13.934  PASSED! Test: Mixed OS Cluster Validates internode connectivity over the vxlan tunnel
10:40:21.68  �[38;5;10m•�[0m
10:40:21.68  PASSED! Test: Mixed OS Cluster Validates cluster by running sonobuoy mixed OS plugin
10:40:21.68  �[38;5;10m•�[0m
10:40:21.68  
10:40:21.68  �[38;5;10m�[1mRan 5 of 5 Specs in 904.181 seconds�[0m
10:40:21.68  �[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
10:40:21.68  --- PASS: TestMixedOSClusterCreateSuite (904.18s)
10:40:21.68  PASS
10:40:21.68  ok  	github.com/rancher/distros-test-framework/entrypoint/mixedoscluster	904.271s