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
the bootstrap helm chart installs argocd using an operator and the template - argocd-install.yaml that speficies the argocd CR for operator to deploy
if we want to update the argcd operator version, or the argocd CR version
how can we do this without having to remove all the applications.argoproj.io
maybe this could just work, not tested. ideally the update process is:
not destructive for the ci-cd stack
rolling update in nature
The text was updated successfully, but these errors were encountered:
@eformat - the operator I think automatically updates itself as I saw in #114 .... I didn't change the operator version and it auotmatically bumped itself to hte newer one whne running a demo this morning. we should keep testing but it should just automagically update the server version too if the operator does in hte base config it uses.
+1 .. i just noted with the push to argocd operator 0.0.6 that it rolled out all by itself .. ! yay for operators and the OLM
agree - need to test the bump of the argo CR as well to see what happens - this is all managed by the operator .. now i think about this .. the operator may have one answer - configure it for HA
Now I think about it, this whole argocd deploy stuff we have here should not exist in this repo. It's a helm chart and should be moved across to the rht-labs helm chart repo and over written from there. I've raised redhat-cop/helm-charts#26 to track that too
the bootstrap helm chart installs argocd using an operator and the template - argocd-install.yaml that speficies the argocd CR for operator to deploy
if we want to update the argcd operator version, or the argocd CR version
how can we do this without having to remove all the applications.argoproj.io
maybe this could just work, not tested. ideally the update process is:
The text was updated successfully, but these errors were encountered: