Open acornett21 opened 4 months ago
I actually don't think the curl <releaseScript> | bash
is all that bad of an installation process. The fact that that's the only place we have it documented isn't ideal though. I'd almost split this into 3 different things to do, in order:
ClusterCatalog
for quay.io/operatorhubio/catalog:latest
to our existing install script./assign
Item number 1 from Joe's message is addressed by MR 1079. Not sure if we should break items 2 and 3 out into separate issues and close this one or if we should track those here.
hi , from what i understand here, you're talking about how OLMV1 will be installed ? because OLMV1, fill the gitops gap from the V0 , you shoudl definitely , add an Helm release of the Operator could be use with some tools like FLuxCD or Argocd
Is running curl and bash from terraform the best option? If so, it’s far from ideal.
Today the install is done from
yamls
from the the release pages, which is less the ideal for end users. We should mimic the install process of OLMv0 (as far as steps go, the mechanism could be different). Sample process below:dependencies
operator-controller