We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Note: In case of v1 cluster, the issue is not occurring and cluster gets deleted. Need to check if we support this scenario for v3.
Steps:
$ kubectl get cluster NAME PHASE AGE VERSION cluster1 Deleting 63m
logs.tar.gz
CAPI cluster should get deleted after fleet repo deletion
Steps mentioned above.
v0.9.0
No response
/kind bug
The text was updated successfully, but these errors were encountered:
Disable CAPI Auto-import on namespace from UI or remove auto-import label on namespace from back-end
From that point forward I think turtles should not be responsible for the "import" functionality.
Sorry, something went wrong.
No branches or pull requests
What steps did you take and what happened?
Note:
In case of v1 cluster, the issue is not occurring and cluster gets deleted. Need to check if we support this scenario for v3.
Steps:
logs.tar.gz
What did you expect to happen?
CAPI cluster should get deleted after fleet repo deletion
How to reproduce it?
Steps mentioned above.
Rancher Turtles version
v0.9.0
Anything else you would like to add?
No response
Label(s) to be applied
/kind bug
The text was updated successfully, but these errors were encountered: