Migrating Siebel CRM Containers to OpenSSL Encryption
This topic describes the steps to migrate Siebel CRM containers to OpenSSL encryption. It includes the following sections:
Starting with Siebel CRM 25.10, you can use an improved encryption model based on OpenSSL libraries when you upgrade existing container-based Siebel CRM deployments from a release earlier than 25.10 to 25.10 or later. The OpenSSL encryption migration affects multiple layers of the Siebel CRM ecosystem, such as Kubernetes workloads, the persistent file system content, and ZooKeeper or registry configuration. As a result, you must follow a controlled upgrade sequence.
You can use SCM to run the encryption migration through an automated process. This process standardizes the steps and helps minimize downtime during the upgrade. The migration process includes the following three phases:
- Pre-encryption migration phase: Scales down key workloads and creates backups and a Git checkpoint tag.
- Encryption migration phase: Runs a Kubernetes job that performs the encryption migration.
- Post-encryption migration phase: Updates manifests to the target version, scales workloads back up, and validates health of the environment.
The automated migration capability gives you a consistent operator experience. It reduces manual work, improves repeatability, and helps you minimize downtime when you upgrade SCM created Siebel CRM environments to Siebel CRM 25.10 or later with OpenSSL-based encryption.