Siebel Cloud Manager deploys Siebel CRM in an OKE orchestrated architecture.

If the "Use existing resources" option is selected at Cloud Manager deployment (meaning that Siebel Cloud Manager will not create an OKE cluster, but use the one provided by the user), during Siebel CRM environment provisioning through REST API POST invocation, payload parameters oke_cluster_id and oke_endpoint together or oke_kubeconfig_path alone is required as input. For more information, see Parameters in Payload Content.

These rules must be satisfied for OKE or else execution workflow fails during resource state validation stage:

• OKE for Siebel CRM should have at-least one Service LB subnet configured. This is required to deploy load balancer during siebel deployment.
• The OKE should not contain namespaces such as <env_name> before deployment, as these namespaces will be used during Siebel environment provisioning.
• At least one node should be in Active state.
• The OKE should be accessible from the CM instance with required polices and VCN peering if necessary should configured before deployment.

You can provision multiple Siebel environments in the same OKE cluster when the "Use Existing Resource" option is selected.

Note: From CM_23.1.0, users can deploy multiple Siebel environments using the same OKE cluster by provisioning each environment in their own namespace.

It is advised to use OKE without any existing flux setup when the "Use Existing Resource" option is selected.

If there is any existing flux setup, you can:

• Either uninstall using the command: flux uninstall all --namespace=<namespace>
• Or upgrade existing flux setup with flag --watch-all-namespaces=false to restrict the scope to watch the namespace where the toolkit is installed.