-
Notifications
You must be signed in to change notification settings - Fork 238
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
Install Retries Can Fail Because Cluster Metadata Exists #87
Comments
Admin kubeconfig too. |
What do we do in the case where there is an existing configmap/secret? Trash/replace? |
I think they fall into the same bucket as the cleanup before install, so yeah I'd trash them if they exist and we're runinng a new install job. |
after discussion the plan is to:
|
fixed with #92 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently we're failing to update status after install (separate issue), but in this case the cluster metadata got uploaded, and install re-tries fail as a result here.
The text was updated successfully, but these errors were encountered: