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
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: