You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 22, 2020. It is now read-only.
As an engineering team we've deployed a bunch of one-off helm install's across our three clusters. We've got a "provisioning" doc with several 'helm install' commands (as many people probably do).
Some of these charts can't be easily torn down and replaced, such as ingress controllers, as they create external resources that DNS is pointing to.
We'd like an option to describe the state of the cluster and then "import" existing releases of charts so that landscaper can take over management of them without disruption of existing services.
The text was updated successfully, but these errors were encountered:
As an engineering team we've deployed a bunch of one-off helm install's across our three clusters. We've got a "provisioning" doc with several 'helm install' commands (as many people probably do).
Some of these charts can't be easily torn down and replaced, such as ingress controllers, as they create external resources that DNS is pointing to.
We'd like an option to describe the state of the cluster and then "import" existing releases of charts so that landscaper can take over management of them without disruption of existing services.
The text was updated successfully, but these errors were encountered: