-
Matthew Fisher authored
When using `helm upgrade --install`, if the first release fails, Helm will respond with an error saying that it cannot upgrade from an unknown state. With this feature, `helm upgrade --install --force` automates the same process as `helm delete && helm install --replace`. It will mark the previous release as DELETED, delete any existing resources inside Kubernetes, then replace it as if it was a fresh install. It will then mark the FAILED release as SUPERSEDED. (cherry picked from commit 13730b0d)
| Name |
Last commit
|
Last update |
|---|---|---|
| .circleci | ||
| _proto | ||
| cmd | ||
| docs | ||
| pkg | ||
| rootfs | ||
| scripts | ||
| testdata | ||
| .gitignore | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| Makefile | ||
| OWNERS | ||
| README.md | ||
| code-of-conduct.md | ||
| glide.lock | ||
| glide.yaml | ||
| versioning.mk |