Closed 3deep5me closed 1 month ago
Hey @3deep5me! Thanks for opening your first issue. We appreciate your contribution and welcome you to our community! We are glad to have you here and to have your input on Contour. You can also join us on our mailing list and in our channel in the Kubernetes Slack Workspace
It was never working correctly, our ingress resources were just created before we changed the names of the envoy services. Its not something which was changed in contour. Its more a "bug" in the chart because --envoy-service-name=
parameter did not get changed.
But it would be still nice to have the option to pass more than one service name to contour.
What steps did you take and what happened: We lately did a update to the newest contour Version (v1.30) (We are using the bitnami helm-chart) After some time we recognized in argocd that ingress objects never get ready. The reason is probably that the
status.loadBalancer
stays empty.We are using this feature https://github.com/bitnami/charts/pull/21994. It allows us to create multiple envoy-services, e.g. in every AZ. This is needed when your cloud-provider do not a provide a multi AZ LB solution. E.g. Hetzner & Scaleway
If we delete 2 of the 3 services, the field gets filled.
What did you expect to happen: Like in versions before the field should look like this:
Or even better like this:
Anything else you would like to add: The Ingress-Object works even the status-filed is not set.
Environment:
kubectl version
): 1.30.2/etc/os-release
): Debian