-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Fix two 'PRISMA' vulnerabilities #6326
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
Conversation
Hi @pmerrison. Thanks for your PR. I'm waiting for a cert-manager member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
389f02f
to
58547f5
Compare
Added sign-off |
Sorry to annoy you with this, but the CI wants both commits to have a signoff message. @pmerrison |
Ah, no worries, sorry I missed one. Will get it fixed up |
Signed-off-by: Paul Merrison <paul@tetrate.io>
Signed-off-by: Paul Merrison <paul@tetrate.io>
58547f5
to
eea043e
Compare
/ok-to-test |
Signed-off-by: Tim Ramlot <42113979+inteon@users.noreply.github.com>
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
@pmerrison: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
Not sure why tests are failing. I tried to include the upgrades in #6332 together will a bunch of other upgrades. |
resolved in #6332 |
Pull Request Motivation
Our enterprise customers complain whenever there are vulnerabilities found in the images we ship, and don't care whether the vulnerabilities are really exploitable or not. To that end, we maintain an internal fork of cert-manager just to apply CVE fixes. I suspect that we might not be the only ones who have customers who are this demanding, so I wanted to submit these fixes upstream since others might find it as helpful to have them as we do.
Kind
Release Note