fluxcd
Common Ingress with Multiple services
HI Team, Just giving a overview of my current environment structure We have a nginx controller at node port, and then we have multiple ingress created and there are many different services which are behind same ingress but are routed based on URI path regex. for example here is the sample ingress
Kind: Ingress . . . spec: ingressClassName: f01f9f rules: - host: api-flaggerfpv1.{{domain}} http: paths: - backend: service: name: f01f9f-ingress-nginx-defaultbackend port: number: 80 path: /healthz pathType: ImplementationSpecific - backend: service: name: f01f9f-qsqsq-admin-svc port: number: 80 path: /service/___/administrator/order-manage(/|$)(.) pathType: ImplementationSpecific - backend: service: name: f01f9f-qdqd-app-svc port: number: 80 path: /service/application/order-manage(/|$)(.) pathType: ImplementationSpecific - backend: service: name: f01f9f-sqidh-internal-svc port: number: 80 path: /sqsqs-internal(/|$)(.*) pathType: ImplementationSpecific . . .
We are trying leverage Flagger with Istio service mesh for all our deployments with A/B testing. when i deploy canary for each services.Deployment , i can see an issue that the canary ingress created by flagger raised an issue saying {"level":"info","ts":"2024-07-25T06:18:50.083Z","caller":"controller/events.go:45","msg":"ingress .......... update error: Operation cannot be fulfilled on ingresses.networking.k8s.io "f01f9f-domains-api-path-ingress-canary": the object has been modified; please apply your changes to the latest version and try again","canary...}
When i troubleshooted i found the issue As there were multiple canary resource Created for different services but they had same ingress, one of the canary resources takes the ownership and hence the above error occurs
I cannot segregate the Ingress as it is the nature of our application , what could be the possible solution for this ??
seems you have to take out the different paths to the separated ingress resource, or there will be conflicts
