Update ingress-nginx to 4.12.0 #765
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![azimuth-automation-bot[bot]](https://avatars.githubusercontent.com/u/109964377?s=60&v=4){kind=small}
azimuth-automation-bot
bot
force-pushed
the
update-dependency/ingress-nginx
branch
from
ea32781 to
1b5038f
Compare
|
Do not merge yet, need to debug issue with CaaS platforms. See #764 |
azimuth-automation-bot
bot
force-pushed
the
update-dependency/ingress-nginx
branch
from
1b5038f to
4b7c426
Compare
|
Looks like this change in Nginx was the cause of the issues we were seeing. TLDR: Security hardening to mitigate CVE that doesn't affect us because we don't allow users to create any ingress resources on the management cluster. |
|
CI failure is due to other flakiness and unrelated to changes in this PR so merging this change anyway. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was created automatically to update ingress-nginx to 4.12.0.