| 2023-10-24 10:59:52 |
Ebrar Leblebici |
description |
Hi,
It seems after we changed the image version with this commit (https://github.com/charmed-kubernetes/charm-kubernetes-worker/commit/dc5386cc6a93ed19afa54cc6b8b11d7eeb43a8a2) the ingress resources are not getting an address.
I reproduced the issue by deploying a Charmed Kubernetes 1.28.3 and creating an ingress object by using the yaml file below:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: cafe-ingress
spec:
ingressClassName: nginx-ingress-controller
rules:
- host: cafe.example.com
http:
paths:
- path: /tea
pathType: Prefix
backend:
service:
name: tea-svc
port:
number: 80
- path: /coffee
pathType: Prefix
backend:
service:
name: coffee-svc
port:
number: 80
And it could not get the address of the nginx-ingress-controller pod:
ubuntu@birru2-bastion:~$ kubectl get ingress
NAME CLASS HOSTS ADDRESS PORTS AGE
cafe-ingress nginx-ingress-controller cafe.example.com 80 70m
Then I changed the container image from "rocks.canonical.com:443/cdk/ingress-nginx/controller:v1.6.4" to "rocks.canonical.com:443/cdk/ingress-nginx/controller:v1.2.0".
kubectl edit daemonset nginx-ingress-controller-kubernetes-worker -n ingress-nginx-kubernetes-worker
It recycled the pod and after the creation of the new ingress controller pod, the ingress got the IP:
ubuntu@birru2-bastion:~$ kubectl get ingress
NAME CLASS HOSTS ADDRESS PORTS AGE
cafe-ingress nginx-ingress-controller cafe.example.com 10.5.0.114 80 76m
Regards,
Ebrar |
Hi,
It seems after we changed the image version with this commit (https://github.com/charmed-kubernetes/charm-kubernetes-worker/commit/dc5386cc6a93ed19afa54cc6b8b11d7eeb43a8a2) the ingress resources are not getting an address with this new version of the image.
I reproduced the issue by deploying a Charmed Kubernetes 1.28.3 and creating an ingress object by using the yaml file below:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: cafe-ingress
spec:
ingressClassName: nginx-ingress-controller
rules:
- host: cafe.example.com
http:
paths:
- path: /tea
pathType: Prefix
backend:
service:
name: tea-svc
port:
number: 80
- path: /coffee
pathType: Prefix
backend:
service:
name: coffee-svc
port:
number: 80
And it could not get the address of the nginx-ingress-controller pod:
ubuntu@birru2-bastion:~$ kubectl get ingress
NAME CLASS HOSTS ADDRESS PORTS AGE
cafe-ingress nginx-ingress-controller cafe.example.com 80 70m
Then I changed the container image from "rocks.canonical.com:443/cdk/ingress-nginx/controller:v1.6.4" to "rocks.canonical.com:443/cdk/ingress-nginx/controller:v1.2.0".
kubectl edit daemonset nginx-ingress-controller-kubernetes-worker -n ingress-nginx-kubernetes-worker
It recycled the pod and after the creation of the new ingress controller pod, the ingress got the IP:
ubuntu@birru2-bastion:~$ kubectl get ingress
NAME CLASS HOSTS ADDRESS PORTS AGE
cafe-ingress nginx-ingress-controller cafe.example.com 10.5.0.114 80 76m
Regards,
Ebrar |
|
