apps: upgrade ingress-nginx controller to 4.13.7 and chart to 1.13.7#2922
Open
kristiangronas wants to merge 1 commit intoelastisys:release-0.50from
Open
apps: upgrade ingress-nginx controller to 4.13.7 and chart to 1.13.7#2922kristiangronas wants to merge 1 commit intoelastisys:release-0.50from
kristiangronas wants to merge 1 commit intoelastisys:release-0.50from
Conversation
Contributor
|
Hello! Thank you for the contribution. Unfortunately this PR will not be merged as (stated in the main README) this repository is deprecated and will not get any further releases. |
This file contains hidden or 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
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.
Warning
This is a public repository, ensure not to disclose:
What kind of PR is this?
Required: Mark one of the following that is applicable:
Optional: Mark one or more of the following that are applicable:
Important
Breaking changes should be marked
kind/admin-changeorkind/dev-changedepending on typeCritical security fixes should be marked with
kind/securityWhat does this PR do / why do we need this PR?
Fixes a high-severity CVE, and ingress-nginx has clusterwide secret access
Information to reviewers
This upgrade mitigates several CVE's have been announced before ingress-nginx's official retirement, including secret disclosure https://discuss.kubernetes.io/t/security-advisory-multiple-issues-in-ingress-nginx/34115
Security notice
Checklist