Skip to content

Support custom argo overrides on spokes - #92

Merged
mbaldessari merged 1 commit into
validatedpatterns:mainfrom
mbaldessari:custom-argo
Jul 30, 2026
Merged

Support custom argo overrides on spokes#92
mbaldessari merged 1 commit into
validatedpatterns:mainfrom
mbaldessari:custom-argo

Conversation

@mbaldessari

Copy link
Copy Markdown
Contributor

If you set the following you can customize the "main" ArgoCD instance we
create on spokes:

acm:
  customArgoYaml:
    controller:
      resources:
        limits:
          cpu: "4"
          memory: 17Gi

This gets deepmerged with the default yaml we normally inject.

Tested with empty customArgoYaml and with the snippet above which got me (sno2 was the spoke):

$ export KUBECONFIG=~/sno2-kubeconfig
$ oc get -n vp-gitops argocd vp-gitops -o jsonpath='{.spec.controller.resources.limits}' | jq .
{
  "cpu": "4",
  "memory": "17Gi"
}

If you set the following you can customize the "main" ArgoCD instance we
create on spokes:

    acm:
      customArgoYaml:
        controller:
          resources:
            limits:
              cpu: "4"
              memory: 17Gi

This gets deepmerged with the default yaml we normally inject.

Tested with empty customArgoYaml and with the snippet above which got me (sno2 was the spoke):

    $ export KUBECONFIG=~/sno2-kubeconfig
    $ oc get -n vp-gitops argocd vp-gitops -o jsonpath='{.spec.controller.resources.limits}' | jq .
    {
      "cpu": "4",
      "memory": "17Gi"
    }
@mbaldessari
mbaldessari requested a review from darkdoc July 29, 2026 13:55
@mbaldessari
mbaldessari merged commit aaad113 into validatedpatterns:main Jul 30, 2026
3 checks passed
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

Successfully merging this pull request may close these issues.

2 participants