Controller fails if a single backend is misconfigured

[karlschriek]

Describe the bug Whenever a single backend is misconfigured the controller fails to apply anything else, for example hitting a "ApplicationGatewayBackendHttpSettingsCannotHaveTrustedRootCertificate" error, but I've seen this on plenty of other errors.

I would expect the controller to skip over incorrectly configured backends and still roll out the ones that are correct!

To Reproduce Misconfigure a backend and see what happens

[Poltergeisen]

We are experiencing this as well for misconfigured WAF policies. Did you have any solution for this?

[karlschriek]

We ended up kicking the Azure application gateway out of our tech stack completely. This was just one of myriad such issues we experienced with it.

On Thu, 23 May 2024, 19:59 Adam, @.***> wrote:

We are experiencing this as well for misconfigured WAF policies. Did you have any solution for this?

— Reply to this email directly, view it on GitHub https://github.com/Azure/application-gateway-kubernetes-ingress/issues/1554#issuecomment-2127745503, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGBE4OE3I6YZYOYZEX4LKGLZDYU7NAVCNFSM6AAAAAAZGLESFOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRXG42DKNJQGM . You are receiving this because you authored the thread.Message ID: <Azure/application-gateway-kubernetes-ingress/issues/1554/2127745503@ github.com>