Committing and Pushing Helm Release Updates

After you update the Helm release YAML files with the required user ID and group ID values, you must review the changes, commit them to the SCM GitOps repository, and then push the commit to the remote repository, as follows:

1. Review the changes in the Helm release YAML files:

   cd /home/opc/siebel/<ENV_ID>/<env_namespace>-cloud-manager
   git status
   git diff

2. Stage the updated files for commit:

   git add flux-crm/apps/base/siebel/*.yaml \
      flux-crm/apps/base/siebel_observability/*.yaml \
      flux-crm/apps/base/siebel-logging/*.yaml \
      flux-crm/metacontroller/release.yaml \
      flux-crm/traefik/traefik-controller/release.yaml

3. Commit the changes to SCM GitOps repository:

   git commit -m "Update runtime IDs for Siebel and observability Helm releases"

4. Push the commit to the remote GitOps repository so that Flux can reconcile the updated desired state:

   git push

   After you push the Helm release changes, Flux reconciles the updated GitOps state and applies the Helm upgrade.

5. Monitor reconciliation until the affected Helm release resources become ready, as follows:

   cd /home/opc/siebel/<ENV_ID>/ source k8sprofile
   flux get helmrelease -n <env_namespace> helm ls -n <env_namespace>
   kubectl get pods -n <env_namespace>

   Wait for reconciliation to complete. Confirm that the affected Helm releases show READY=True.

6. Check the Helm status:

   helm ls -n <env_namespace>

   Confirm that the affected releases show STATUS=deployed.

7. Check the pod status:

   kubectl get pods -n <env_namespace>

   Confirm that the affected pods are running successfully.