-
Notifications
You must be signed in to change notification settings - Fork 413
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Controller fails if a single backend is misconfigured #1554
Comments
karlschriek
changed the title
Controller fails if a single backend is misconfigure
Controller fails if a single backend is misconfigured
Jun 14, 2023
We are experiencing this as well for misconfigured WAF policies. Did you have any solution for this? |
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
<#1554 (comment)>,
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>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
The text was updated successfully, but these errors were encountered: