High-Level Steps for Installing Siebel Monthly Update in a Siebel CRM Environment Deployed using SCM

You can use the procedure in this topic to install latest monthly updates in a Siebel CRM environment deployed using SCM. These steps do not include repository upgrade steps, which are optional and identical to those relevant for on-premises Siebel CRM deployments.

The following are the high-level steps to install a Siebel monthly update in a Siebel CRM environment deployed using SCM:

Note: For detailed steps to install a Siebel monthly update, see Installing Siebel Monthly Update in a Siebel CRM Environment Deployed by SCM.

1. Back up the database.
2. Upgrade SCM.
3. Back up the SCM files for the Siebel environment.
4. Tag Git repositories.
5. Update SCM container images to the user's container registry.
6. Update secrets with the user's container registry details.
7. Update Helmchart and Helm release.

   You must update the Helm chart repository (/home/opc/siebel/<ENV_ID>/<env_namespace>-helmcharts/) to the latest version and Helm release (/home/opc/siebel/<ENV_ID>/<env_namespace>-cloud-manager) to point to the user's container registry for the following:

   • Infrastructure(ingress-nginx)
   • Metacontroller (metacontroller)
   • SiebelOperator (siebel-operator)
   • SiebelGateway (siebel-gateway)
   • SiebelConfig (siebel-config)
   • Siebel (siebel)
   • SiebelArtifacts (siebel-artifacts)
   • SiebelObservability (siebel_observability)
8. Build and push the new Siebel CRM custom image for the target version.
9. Update the SCM repository files with the newly built target Siebel CRM Image.
10. Check the status of the flux components after upgrade.
11. Monitor the successful completion of postinstalldb Kubernetes job.
12. Execute configuration instructions specific to a release.
13. Upgrade the repository.
14. Troubleshoot any issues.
15. Rollback steps for Helm charts.
16. Verify the application URLs once the environment comes up.