Change GitOps-Managed Components

To change an existing deployment on k8s-admin, edit values.yaml and run the publish playbook again, then check the result in Argo CD.

This procedure applies to GitOps-managed components, not components installed by the BCM Kubernetes wizard, such as Grafana and Loki.

Edit the Values File

On the machine where you installed the Ansible collection, edit the values.yaml used for installation. Keep the full file, including repository settings, release-pinned versions, and settings for the other components.

To disable a component, set its enabled setting to false. Do not delete its configuration block: omitted settings can default to enabled.

Warning

Removal deletes managed resources and can delete persistent data. Back up required data first. Remove dependent workloads before shared services and operators. Keep Argo CD enabled so it can apply the changes.

For example, to disable Launchpad, change its existing block as follows while keeping the other settings in that block:

launchpad:
  enabled: false
  # Keep the existing version, syncWave, and other Launchpad settings.

This removes the Launchpad Application, not Keycloak or the shared gateway.

Publish the Change

On the same machine, run the render-and-publish command with your updated values.yaml:

export NGC_API_KEY=<ngc-api-key>
ansible-playbook nvidia.nmc.deploy_argocd_gitops \
  -i "<head-node-ip>," \
  -u root \
  -e @values.yaml

Check the Result

On the active BCM head node, check the Applications and the Git revision that root has synchronized:

module load kubernetes/k8s-admin
kubectl -n argocd get applications
kubectl -n argocd get application root -o jsonpath='{.status.sync.revision}{"\n"}'

Wait for root to reach the latest commit shown for your configured branch in the Git repository web UI. It and all remaining Applications must become Synced and Healthy. A removed component’s Application must disappear; for the example, k8s-admin-launchpad is no longer listed. Persistent volumes can remain, depending on the component’s retention policy.

If the Change Does Not Complete

Use Troubleshooting to inspect the failing Application and its workloads. Do not delete root or a child Application to retry a deployment: deletion can cascade to workloads and persistent data.