-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
cert-manager: Fix incorrect leader election namespace lead to insufficient permission #8433
cert-manager: Fix incorrect leader election namespace lead to insufficient permission #8433
Conversation
Hi @rtsp. Thanks for your PR. I'm waiting for a kubernetes-sigs 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. |
Thanks @rtsp for following up on this! /ok-to-test |
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.
@rtsp 👍
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: floryut, rtsp 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 |
Hi everyone, @rtsp
I guess there are some permissions missing
|
@red55 Which kubespray branch or commit you're using? Try updating to the latest commit, if the problem still occur please open new issue and provide information as much as possible. Feel tree to mention me or this PR from those new issue. |
@rtsp hi,
|
@red55 I didn't test the latest commit yet but it seems to sync with upstream cert-manager manifest. I'm not sure which system you're running. May be you don't have permission on kube-system namespace on your system? You clould try changing Anyway please open a bug report and provide more information here https://github.com/kubernetes-sigs/kubespray/issues/new?assignees=&labels=kind%2Fbug&template=bug-report.md Thanks |
…fixes from master - cert-manager: Fix incorrect leader election namespace lead to insufficient permission (kubernetes-sigs#8433) - cert-manager: Allow to change leader election namespace for GKE Autopilot support (kubernetes-sigs#8424)
…fixes from master cherry-picked from * ccd3180 cert-manager: Fix incorrect leader election namespace lead to insufficient permission (kubernetes-sigs#8433) * e791089 cert-manager: Allow to change leader election namespace for GKE Autopilot support (kubernetes-sigs#8424)
What type of PR is this?
/kind bug
What this PR does / why we need it:
My last PR #8424 fix the GKE Autopilot problem but not the original problem reported in #8393 (at least it didn't break anything).
kubespray/roles/kubernetes-apps/ingress_controller/cert_manager/templates/cert-manager.yml.j2
Lines 629 to 633 in cee481f
Referring to official cert-manager manifest. The leader election namespace is
kube-system
, notcert-manager
. so the metadata.namespace here (and other 3 places) should be thecert_manager_leader_election_namespace
(which I introduced in #8424) instead ofcert_manager_namespace
.This PR change namespace configurations in
cert-manager.yml.j2
to match the upstream cert-manager manifests which use kube-system by default and allow overriding withcert_manager_leader_election_namespace
variable.Which issue(s) this PR fixes:
Fixes #8393
Special notes for your reviewer:
Does this PR introduce a user-facing change?: