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 Jul 10, 2021. It is now read-only.
From Chad Tripod @ Armory:
Could we put on the backlog a refresh of our HELM3 docs? In the past month I've talked with several organizations finally getting to the maturity stage with Kubernetes that they're packaging apps in HELM for their developers to input values into for each env. It will also need an equivalent chart Using Spinnaker HELM3 vs using HELM upgrade directly on the cluster as there is release capabilities for blue/green which Spinnaker likes to own.
The docs need to move to HELM3. Nobody uses HELM2 as it required tiller (an agent that ran in Kubernetes for HELM) and really was a first run at templating kubernetes configs. It should be assumed moving forward ALL orgs will use HELM3.
The text was updated successfully, but these errors were encountered:
https://spinnaker.io/guides/user/kubernetes-v2/deploy-helm/
From Chad Tripod @ Armory:
Could we put on the backlog a refresh of our HELM3 docs? In the past month I've talked with several organizations finally getting to the maturity stage with Kubernetes that they're packaging apps in HELM for their developers to input values into for each env. It will also need an equivalent chart Using Spinnaker HELM3 vs using HELM upgrade directly on the cluster as there is release capabilities for blue/green which Spinnaker likes to own.
The docs need to move to HELM3. Nobody uses HELM2 as it required tiller (an agent that ran in Kubernetes for HELM) and really was a first run at templating kubernetes configs. It should be assumed moving forward ALL orgs will use HELM3.
The text was updated successfully, but these errors were encountered: