Examining Your Deployment

You can examine the Kubernetes deployment with kubectl, such as in the following commands run on the virtual machine for SCM. This topic is part of Troubleshooting a Siebel Cloud Manager Instance or Requested Environment.

sudo podman exec -it cloudmanager bash

source /home/opc/siebel/<env_id>/k8sprofile

kubectl -n <deployment name supplied in deployment POST request> get all

The last command shown above displays information about all the Kubernetes objects that were created for a given Siebel CRM environment when it was deployed on OCI (which might have been subsequently modified through making incremental changes). These objects or pods correspond to instances (and replicas) of Siebel Server, Siebel Gateway (CGW), Siebel Application Interface (SAI), and Siebel Management Console (SMC). Also present are an ingress controller to control ingress to proxy servers, and a metacontroller and a Siebel controller for executing incremental changes.

You can compare the information displayed by this kubectl command to the representation of the deployment and its primary elements in SMC.