-
Notifications
You must be signed in to change notification settings - Fork 66
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
Installing the helm chart without the --wait parameter fails #406
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/test-infra repository. |
I'm not sure that we can fix this, controllers need to start for webhooks to work. Only after controller is up operator CRs can be applied. |
Not the cleanest of all approaches but we could create a Job with a check (e.g. curl) if the webhook works yet. If so the Job terminates. The job than has to be installed with a post-install weight that is lower than the one that failed. In case a desperate flux user is reading this: |
Is this something that we want to fix? I verified that creating a Job with a webhook check solves this problem: https://github.com/kubernetes-sigs/cluster-api-operator/compare/main...willie-yao:cluster-api-operator:no-wait?expand=1 Not sure if this is something we want to include and maintain as part of the chart though. I've also added warnings about the |
What steps did you take and what happened:
Fails with the following output
What did you expect to happen:
I expected the helm chart to install successfully
Anything else you would like to add:
If you add the
--wait
parameter it worksEnvironment:
kubectl version
): v1.28.3/etc/os-release
):/kind bug
[One or more /area label. See https://github.com/kubernetes-sigs/cluster-api-operator/labels?q=area for the list of labels]
The text was updated successfully, but these errors were encountered: