-
Notifications
You must be signed in to change notification settings - Fork 61
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
Secret "capi-operator-webhook-service-cert" is not automatically created #520
Comments
This issue is currently awaiting triage. If CAPI Operator contributors determines this is a relevant issue, they will accept it by applying the The 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-sigs/prow repository. |
Hi @henrypham67 you said that you deployed like it was described in the quickstart guide. I assume that you deployed cert-manager with the capi-operator. Maybe this is a timing issue that you can fix by deploying cert-manager manually upfront (for test) |
Hi @mxmxchere thank you for your response, I gave it a try and am still getting the issue |
okay, the missing secret should be generated by the cert-manager. I think you have to find out what is stuck there. You can start to look for errors by inspecting the cert resource
|
It's weird because I can not find any certificate using the command |
Ok, as far as i can see the cert is defined in the file
|
Thank you for your recommendation, I am now able to install CAPI Operator. I installed the |
What steps did you take and what happened:
[A clear and concise description on how to REPRODUCE the bug.]
I followed the Quick Start Operator and got the
secret "capi-operator-webhook-service-cert" not found
error from pod ofcapi-operator-cluster-api-operator
deploymentWhat did you expect to happen:
The operator chart should be installed successfully
Environment:
kubectl version
): v1.29.2/etc/os-release
): Ubuntu 22.04.4 LTS/kind bug
The text was updated successfully, but these errors were encountered: