feat(argo-cd): allow disabling individual Argo CD components#3814
Open
C4tWithShell wants to merge 4 commits intoargoproj:mainfrom
Open
feat(argo-cd): allow disabling individual Argo CD components#3814C4tWithShell wants to merge 4 commits intoargoproj:mainfrom
C4tWithShell wants to merge 4 commits intoargoproj:mainfrom
Conversation
Signed-off-by: C4tWithShell <vladimir.shelkovnikov@aiso.team>
Signed-off-by: C4tWithShell <vladimir.shelkovnikov@aiso.team>
Signed-off-by: C4tWithShell <vladimir.shelkovnikov@aiso.team>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description:
Adds
enabledboolean flags to the four main Argo CD components - controller, server, repoServer, and applicationSet. Each can be individually excluded from the rendered Helm manifests. All flags default to true, making this backwards-compatible.Why this is useful: In split/agent-based Argo CD deployments (e.g. argocd-agent), not all components run in every cluster. For example, a spoke cluster may only need the application controller, while the hub runs the server and repo-server. Previously, users had to work around this with post-render patches or separate chart installations.
Checklist: