Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HMW update argocd CR or operator version using rolling update methodology #110

Open
eformat opened this issue Apr 16, 2020 · 3 comments
Open

Comments

@eformat
Copy link
Member

eformat commented Apr 16, 2020

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
@springdo
Copy link
Contributor

@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.

https://github.com/operator-framework/olm-book/blob/master/docs/subscriptions.md#manually-approving-upgrades-via-subscriptions

@eformat
Copy link
Member Author

eformat commented Apr 18, 2020

+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

https://argocd-operator.readthedocs.io/en/latest/usage/ha/

perhaps then updates/rollouts to operator and argocd can be fairly seamless to development teams

@springdo
Copy link
Contributor

You can make it HA very easily and we actually turned it off when trying to figure out why it was spinning up and tearing down the server every 60 seconds. If you look here you can see it -https://github.com/rht-labs/ubiquitous-journey/blob/master/bootstrap/templates/argocd-install.yaml#L78

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants