Giters

linode / apl-core

Application Platform for Linode Kubernetes Engine (and any other conformant K8s)

Home Page:https://otomi.io

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

ArgoCD pending when otomi.nodeSelector is set

j-zimnowoda opened this issue · comments

commented

Describe the bug: (a clear and concise description of what the bug is)

To Reproduce
Steps to reproduce the behavior:

  1. Deploy cluster with two node pool (one dedicated to otomi core apps)
  2. Deploy otomi with argocd enabled and otomi.nodeSelector set to designated node pool
  3. Observe that argoCD pods are in Pending state

Expected behavior: (a clear and concise description of what you expected to happen)
ArgoCD pods deploys to designated node pool as all other

Additional context: (add any other context about the problem here)
The node placement through the values otomi.nodeSelector.
Then OPA Gatekeeper via the mutation webhook adds nodeAffinity to Pods.
One exception is the ArgoCD CR which has its own nodePlacement section.

Also note that the argocd item in line 72 in the charts/gatekeeper-artifacts/templates/_helpers.tpl file is not a good place, because the gatekeeper-artifacts.namespaces definition is used by three "mutations" that are defined in the charts/gatekeeper-artifacts/templates/mutations.yaml file.

Refer to:

  • values/argocd-operator/argocd-operator-cr.gotmpl
  • charts/gatekeeper-artifacts/templates/mutations.yaml
  • charts/gatekeeper-artifacts/templates/_helpers.tpl
commented

Released in v2.8.1