Using CRDs with multi-clusters #1350
Unanswered
arthurcogo
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm trying to migrate from using annotations to the new CRDs with v1 🙌 However, I'm not sure of the best way to configure things for our setup.
We have two clusters. ArgoCD runs on cluster
A, where all of our Applications are defined. Some of those Applications are deployed on clusterB. Image updater runs on clusterAonly.With annotations this was straightforard, because I just added the annotations to the Applications on cluster
Aand it was away.When attempting to migrate, I removed the annotations and used the new ImageUpdater CRDs for each application instead. What I didn't foresee was that the application attempted to deploy the ImageUpdater resources to the target cluster alongside the other resources, but that doesn't work on cluster
Bbecause it doesn't have image updater installed and therefore doesn't have the CRDs.It seems the expected solution is to deploy the ImageUpdater resources in cluster
A... but this means they're decoupled from the application they are updating (as there is no way to deploy one application on two clusters).Am I missing something? Does anyone else have a good solution for this?
For context, this is what I'm trying to migrate from annotation-based to CRD-based:
Ausing a semver update strategyBusing a digest strategy on theedgetagBusing a digest strategy on thepr-<number>tagBeta Was this translation helpful? Give feedback.
All reactions