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
In the quickstart guide, we use kubectl for most install steps and helm for one step. It'd be nice if there was a path for an all helm (or mostly helm) installation path and another one that just uses kubectl.
One argument for not using helm for all or most of the steps is that we are installing CRDs which is a cluster wide resource and operators may not want to use Helm for installing CRDs and also upgrades are tricky. Considering this is a quickstart, we should favor ease of installation and point to a diff doc that talks about what to consider when installing in prod environments. There is some guidance on how to deal with CRDs on this helm doc . Here is what cert-manager does with CRDs in their helm install path.
The text was updated successfully, but these errors were encountered:
In the quickstart guide, we use kubectl for most install steps and helm for one step. It'd be nice if there was a path for an all helm (or mostly helm) installation path and another one that just uses kubectl.
One argument for not using helm for all or most of the steps is that we are installing CRDs which is a cluster wide resource and operators may not want to use Helm for installing CRDs and also upgrades are tricky. Considering this is a quickstart, we should favor ease of installation and point to a diff doc that talks about what to consider when installing in prod environments. There is some guidance on how to deal with CRDs on this helm doc . Here is what cert-manager does with CRDs in their helm install path.
The text was updated successfully, but these errors were encountered: