-
Notifications
You must be signed in to change notification settings - Fork 20
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
Prow: Update ingress-nginx to v1.9.4 #591
Prow: Update ingress-nginx to v1.9.4 #591
Conversation
This bumps the ingress-nginx version and enables mitigations for 3 CVEs. - GHSA-5wj4-wffq-3378 - GHSA-gvrm-w2f9-f77q - GHSA-fp9f-44c2-cw27 The CVEs are all rated High, but require that the attacker has access to the Kubernetes cluster and is able to create or modify annotations on the ingress resources.
This is irrelevant |
@lentzi90: Overrode contexts on behalf of lentzi90: test-ubuntu-integration-main In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/cc @tuminoid (since security related) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tuminoid The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
This bumps the ingress-nginx version and enables mitigations for 3 CVEs.
The CVEs are all rated High, but require that the attacker has access to the Kubernetes cluster and is able to create or modify annotations on the ingress resources.
Note: Future versions of ingress-nginx may enable these mitigations by default, at which point we can remove these extra patches.
The changes has been applied in the cluster. ✔️