-
Notifications
You must be signed in to change notification settings - Fork 155
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
[release/v2.16] fix cert-manager validating webhook #6741
[release/v2.16] fix cert-manager validating webhook #6741
Conversation
/lgtm |
LGTM label has been added. Git tree hash: 1ac7f78f7c19829e57278303a8c1701e88c1c735
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rastislavs, xrstf 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 |
/cherrypick release/v2.15 |
@xrstf: once the present PR merges, I will cherry-pick it on top of release/v2.15 in a new PR and assign it to you. 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. |
@xrstf: new pull request created: #6742 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. |
/cherrypick release/v2.14 |
@xrstf: #6741 failed to apply on top of branch "release/v2.14":
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. |
What this PR does / why we need it:
When setting up the Helm chart, I accidentally copypasted the wrong path here. This can lead to errors like
In the master branch, #6739 takes care of updating and fixing cert-manager.
Does this PR introduce a user-facing change?: