Is there an existing issue for this?

• I have searched the existing issues

What happened?

When deploying an ingress entry for Cilium and changing the ingressClass to something else first Cilium will keep all created resources around.

To reproduce:

1. Deploy ingress + an example app: https://docs.cilium.io/en/v1.12/gettingstarted/servicemesh/ingress/#gs-ingress
2. check if the LB service got created kubectl get service
3. kubectl edit ingress (or apply a change) and change ingressClass to something else (like nginx)
4. check kubectl get service and still see the LB service

Cilium Version

latest master and v1.12.5

Kernel Version

n/a

Kubernetes Version

v1.26.1

Sysdump

No response

Relevant log output

No response

Anything else?

The update ingress checks only the new ingress field ingressClass := getIngressClassName(event.newIngress)
It should also be handled correct on operator startup to check any changes while it was down.

Code of Conduct

• I agree to follow this project's Code of Conduct