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
After an unsuccessful first installation (a trivial ctrl+c on helm), some resources remain configured.
It would be useful to have a procedure to completely clean up the installation and be able to relaunch it
client.go:486: [debug] Starting delete for "default" DataStore client.go:490: [debug] Ignoring delete failure for "default" kamaji.clastix.io/v1alpha1, Kind=DataStore: datastores.kamaji.clastix.io "default" not found client.go:142: [debug] creating 1 resource(s) Error: INSTALLATION FAILED: failed pre-install: warning: Hook pre-install kamaji/templates/datastore.yaml failed: 1 error occurred: * Internal error occurred: failed calling webhook "vdatastore.kb.io": failed to call webhook: Post "[https://kamaji-webhook-service.kamaji-system.svc:443/validate-kamaji-clastix-io-v1alpha1-datastore?timeout=10s](https://kamaji-webhook-service.kamaji-system.svc/validate-kamaji-clastix-io-v1alpha1-datastore?timeout=10s)": service "kamaji-webhook-service" not found helm.go:84: [debug] failed pre-install: warning: Hook pre-install kamaji/templates/datastore.yaml failed: 1 error occurred: * Internal error occurred: failed calling webhook "vdatastore.kb.io": failed to call webhook: Post "[https://kamaji-webhook-service.kamaji-system.svc:443/validate-kamaji-clastix-io-v1alpha1-datastore?timeout=10s](https://kamaji-webhook-service.kamaji-system.svc/validate-kamaji-clastix-io-v1alpha1-datastore?timeout=10s)": service "kamaji-webhook-service" not found
The text was updated successfully, but these errors were encountered:
@m4oc thanks for reporting this Marco. We'll provide a recovery procedure in the doc.
Sorry, something went wrong.
@m4oc please check #389
bsctl
Successfully merging a pull request may close this issue.
After an unsuccessful first installation (a trivial ctrl+c on helm), some resources remain configured.
It would be useful to have a procedure to completely clean up the installation and be able to relaunch it
The text was updated successfully, but these errors were encountered: