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 pulling the latest master I get several issues when running the example projects:
Error: UPGRADE FAILED: "ingress-controller" has no deployed releases
Error: release ingress-controller failed: clusterroles.rbac.authorization.k8s.io "ingress-controller-nginx-ingress" already exists
Error: release system failed: configmaps "alertmanager-config" already exists
Running garden init env --force seems to solve these issues. We should suggest that in the error message.
garden init env --force
The text was updated successfully, but these errors were encountered:
Haven't seen this in awhile so closing for now.
Sorry, something went wrong.
No branches or pull requests
After pulling the latest master I get several issues when running the example projects:
Error: UPGRADE FAILED: "ingress-controller" has no deployed releases
Error: release ingress-controller failed: clusterroles.rbac.authorization.k8s.io "ingress-controller-nginx-ingress" already exists
Error: release system failed: configmaps "alertmanager-config" already exists
Running
garden init env --force
seems to solve these issues. We should suggest that in the error message.The text was updated successfully, but these errors were encountered: