fix: moving to registry.k8s.io images to avoid bitnami image removal

Author: InputObject2

kubernetes/overrides/ingress-private/values.yaml

@@ -1,6 +1,10 @@
+global:
+  security:
+    allowInsecureImages: true
+
 image:
   registry: docker.io
-  repository: bitnami/nginx-ingress-controller
+  repository: bitnamilegacy/nginx-ingress-controller
   tag: 1.12.1-debian-12-r0
 
 electionID: ingress-controller-leader
@@ -31,6 +35,10 @@ resources:
 
 defaultBackend:
   replicaCount: 2
+  image:
+    registry: docker.io
+    repository: bitnamilegacy/nginx
+    tag: 1.29.1-debian-12-r0
   pdb:
     create: false
   resources:

kubernetes/overrides/ingress-public/values.yaml

@@ -1,6 +1,10 @@
+global:
+  security:
+    allowInsecureImages: true
+
 image:
   registry: docker.io
-  repository: bitnami/nginx-ingress-controller
+  repository: bitnamilegacy/nginx-ingress-controller
   tag: 1.12.1-debian-12-r0
 
 electionID: ingress-controller-public-leader
@@ -28,6 +32,10 @@ resources:
 
 defaultBackend:
   replicaCount: 2
+  image:
+    registry: docker.io
+    repository: bitnamilegacy/nginx
+    tag: 1.29.1-debian-12-r0
   pdb:
     create: false
   resources: