The core GitOps workflow requires that you make a change in Git, push it, and let your controller apply it.
Update tenant values and configurations
Update values: Overwrite the
tenant-values.yamlfile with the newly downloaded file from Cortex, commit, and push.Update chart version: Delete the old
konnector-bundledirectory, runhelm pullto download the new<NEW_VERSION>, commit, and push.Add inline overrides: Add specific configurations to your
helmrelease-patch.yaml(Flux) orapplication.yaml(ArgoCD) . Inline values have the highest priority and will override both the chart defaults andtenant-values.yaml.
Namespace configuration
The target namespace is controlled by the global.namespace parameter in tenant-values.yaml (default: panw). If changing the namespace, you must update it in three places:
global.namespaceintenant-values.yaml.The ConfigMap namespace in
overlays/.../kustomization.yaml.The target namespace in
helmrelease-patch.yaml(Flux) orspec.destination.namespaceinapplication.yaml(ArgoCD).
Day-to-day operations
Suspend/disable auto-sync:
Flux:
Run flux suspend helmrelease kspm-agent -n panwor setsuspend:truein your HelmRelease spec via Git.ArgoCD: Run
argocd app set kspm-agent --sync-policy noneor remove theautomated:block from your Application spec via Git.
Manual reconciliation/sync:
Flux:
flux reconcile kustomization kspm-agent<TENANT_ID>.ArgoCD:
argocd app sync kspm-agent
Uninstall a release:
Flux: Delete the Flux Kustomization (
flux delete kustomization kspm-agent-<TENANT_ID>) to cascade and remove all managed resources.ArgoCD: Delete the ArgoCD Application with the cascade flag (
argocd app delete kspm-agent --cascade).
Note
For Proof of Concept testing, the repository includes a deploy-gitlab.sh script to deploy a self-hosted GitLab EE server directly on your cluster.