[Release-1.29] - Bump Ingress-Nginx to v1.12

[dereknola]

Backport fix for Bump Ingress-Nginx to v1.12

• Bump Ingress-Nginx to v1.12 #7549

[fmoral2]

Validated on Version:

-$ rke2  v1.29.13+rke2r1 

Environment Details

Infrastructure
Cloud EC2 instance

Node(s) CPU architecture, OS, and Version:
NAME="Oracle Linux Server"
VERSION="8.9"
ID="ol"
ID_LIKE="fedora"

Cluster Configuration:
1 node servers

Steps to validate the fix

1. Install rke2
2. Verify ngnix-ingress-controller version
3. Validate nodes and pods

Validation Results:

 Command:
 kubectl get node -o yaml  --kubeconfig=/tmp/fmoralsasdasddsadsaddasdadsaddasda_kubeconfig  | grep 'nginx-ingress-controller' -A1
 ---------------------
 Assertion:
 ingress
 ----------------------
 Matched with result:
 - docker.io/rancher/nginx-ingress-controller@sha256:2607ab5b9d933fa887e44d4bfc329b1fb178f7ff08ec60a17e5dfb06917944ad
       - docker.io/rancher/nginx-ingress-controller:v1.12.0-hardened2
       sizeBytes: 298300341


 Cluster nodes:                             
07:37:44  ip-us-east-2.compute.internal   Ready   control-plane,etcd,master   4m    v1.29.13+rke2r1      Ubuntu 24.04 LTS   6.8.0-1012-aws   containerd://1.7.23-k3s2


Cluster pods:                              
07:42:21  kube-system   cloud-controller-manager-ip-us-east-2.compute.internal   1/1   Running     0     8m12s   172.31.8.251   ip-us-east-2.compute.internal   <none>   <none>
07:42:21  kube-system   etcd-ip-us-east-2.compute.internal                       1/1   Running     0     7m58s   172.31.8.251   ip-us-east-2.compute.internal   <none>   <none>
07:42:21  kube-system   helm-install-rke2-canal-b5p68                                         0/1   Completed   0     7m25s   172.31.8.251   ip-us-east-2.compute.internal   <none>   <none>
07:42:21  kube-system   helm-install-rke2-coredns-lwvsr                                       0/1   Completed   0     7m24s   172.31.8.251   ip-us-east-2.compute.internal   <none>   <none>
07:42:21  kube-system   helm-install-rke2-ingress-nginx-cjqsm                                 0/1   Completed   0     7m24s   10.42.0.5      ip-us-east-2.compute.internal   <none>   <none>
07:42:21  kube-system   helm-install-rke2-metrics-server-mg2zd                                0/1   Completed   0     7m24s   10.42.0.4      ip-us-east-2.compute.internal   <none>   <none>
07:42:21  kube-system   helm-install-rke2-runtimeclasses-p9rwf                                0/1   Completed   0     7m23s   10.42.0.8      ip-us-east-2.compute.internal   <none>   <none>
07:42:21  kube-system   helm-install-rke2-snapshot-controller-4qzpb                           0/1   Completed   1     7m23s   10.42.0.3      ip-us-east-2.compute.internal   <none>   <none>
07:42:21  kube-system   helm-install-rke2-snapshot-controller-crd-z8pxx                       0/1   Completed   0     7m23s   10.42.0.6      ip-us-east-2.compute.internal   <none>   <none>
07:42:21  kube-system   kube-apiserver-ip-us-east-2.compute.internal             1/1   Running     0     8m35s   172.31.8.251   ip-us-east-2.compute.internal   <none>   <none>
07:42:21  kube-system   kube-controller-manager-ip-us-east-2.compute.internal    1/1   Running     0     8m14s   172.31.8.251   ip-us-east-2.compute.internal   <none>   <none>
07:42:21  kube-system   kube-proxy-ip-us-east-2.compute.internal                 1/1   Running     0     8m35s   172.31.8.251   ip-us-east-2.compute.internal   <none>   <none>
07:42:21  kube-system   kube-scheduler-ip-us-east-2.compute.internal             1/1   Running     0     7m35s   172.31.8.251   ip-us-east-2.compute.internal   <none>   <none>
07:42:21  kube-system   rke2-canal-vllrl                                                      2/2   Running     0     6m34s   172.31.8.251   ip-us-east-2.compute.internal   <none>   <none>
07:42:21  kube-system   rke2-coredns-rke2-coredns-58664888cf-5lcjn                            1/1   Running     0     6m59s   10.42.0.2      ip-us-east-2.compute.internal   <none>   <none>
07:42:21  kube-system   rke2-coredns-rke2-coredns-autoscaler-7dfbb46d5d-czk6w                 1/1   Running     0     6m59s   10.42.0.7      ip-us-east-2.compute.internal   <none>   <none>
07:42:21  kube-system   rke2-ingress-nginx-controller-btm5s                                   1/1   Running     0     114s    10.42.0.12     ip-us-east-2.compute.internal   <none>   <none>
07:42:21  kube-system   rke2-metrics-server-8599b78c6d-mfnhz                                  1/1   Running     0     2m56s   10.42.0.9      ip-us-east-2.compute.internal   <none>   <none>
07:42:21  kube-system   rke2-snapshot-controller-55d765465-d8jnp                              1/1   Running     0     2m28s   10.42.0.11     ip-us-east-2.compute.internal   <none>   <none>



                     
07:47:04  namespace/test-ingress created
07:47:04  networkpolicy.networking.k8s.io/ingress-to-backends created
07:47:04  ingress.networking.k8s.io/test-ingress created
07:47:04  service/nginx-ingress-svc created
07:47:04  replicationcontroller/test-ingress created
07:47:04  networkpolicy.networking.k8s.io/allow-all-ingress created
07:47:04  
  
  Command:
  kubectl get pods -n test-ingress -l k8s-app=nginx-app-ingress --field-selector=status.phase=Running  --kubeconfig=/tmp/fmoralsasdasddsadsaddasdadsaddasda_kubeconfig
  ---------------------
  Assertion:
  Running
  ----------------------
  Matched with result:
  NAME                 READY   STATUS    RESTARTS   AGE
  test-ingress-8zhml   1/1     Running   0          5s
   test-ingress-q44xn   1/1     Running   0          5s                   
 
 PASSED! Components Version Upgrade: Verifies Ingress