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

reflect ci/cd releases in the gitops repository #24

Open
romaninsh opened this issue Jan 7, 2021 · 0 comments
Open

reflect ci/cd releases in the gitops repository #24

romaninsh opened this issue Jan 7, 2021 · 0 comments

Comments

@romaninsh
Copy link
Member

romaninsh commented Jan 7, 2021

New GitOps flow (see https://codefresh.io/features/gitops/) requires kubernetes yaml files to be versioned in a separate repository. We currently store that in "apps" folder - and reference some stable branch. CI/CD process uses "patch" when deploying new image from codefresh and argocd is configured to ignore change in image tag.

This is wrong use of GitOps instead it should follow the guide - release from ci/cd (e.g. new atk.ui demo) should commit new tag into the infrastructure repo (or some other repo), this should then be picked up by the cluster and sync into a new state.

Several things would need to be refactored for this.

This should address problem where application state reverts back to older version and would also allow us to ditch DO credentials in codefresh that has been expiring/failing periodically.

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

1 participant