-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Tilt no longer appears to install cert-manager and fails to start up #7100
Comments
@Skarlso: This issue is currently awaiting triage. If CAPI 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. |
This is the offending PR: https://github.com/kubernetes-sigs/cluster-api/pull/6483/files Aaaa... And here and now I see this OFC:
Ok, this fixed my issue. |
Agree. Thx for reporting this issue. Looks like #6483 changed the default behavior. I'll open a PR to change that back. /reopen |
@sbueringer: Reopened this issue. 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. |
Ah yes. :) Thanks! :)) 👍 |
Thank you! :) |
What steps did you take and what happened:
[A clear and concise description on how to REPRODUCE the bug.]
Run
tilt up
on a clean kind cluster.What did you expect to happen:
Error:
I have nothing else. It worked a couple commits ago...
This issue can be worked around if I run
clusterctl init --provider aws
. That installs cert-manager and things work from there on.Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version
): 1.22/etc/os-release
): OSXTilt setting:
/kind bug
[One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels]
The text was updated successfully, but these errors were encountered: