For Netcool® Operations Insight® (NOI) on RedHat Openshift Container Platform (OCP)

Preparing credentials for authentication

If you are connecting to an ObjectServer on RedHat Openshift Container Platform (OCP), you need to extract the CA certificate from the Proxy deployed with the NOI deployment and use the proxy to secure the connection using TLS. For more information on how to get the connection details and the proxy certificate, see Connecting with the proxy service.

Retrieve the ObjectServer authentication credentials:

 NOI_INSTANCE=<noi instance>
 NOI_NAMESPACE=<noi namespace>
 NOI_OMNI_USERNAME=root
 NOI_OMNI_PASSWORD=$(kubectl get secret -n $NOI_NAMESPACE $NOI_INSTANCE-omni-secret -o jsonpath='{.data.OMNIBUS_ROOT_PASSWORD}' | base64 --decode && echo)

Where:

<noi instance> is the NOI instance name.

<noi namespace> is the NOI instance namespace.

Extracting server certificates for SSL communication

If the ObjectServer TLS certificate is not signed by a trusted CA or the Openshift Certificate Authority (CA) signer certificate, extract the TLS Certificate from the ObjectServer. The example below will extract the NOI proxy tls.crt file into the local directory.

NOI_INSTANCE=noi-evtmgr
NOI_NAMESPACE=noi
oc extract secret/$NOI_INSTANCE-proxy-tls-secret -n $NOI_NAMESPACE --to=. --keys=tls.crt 

Create a probe-server communication secret

After the preparing the required files, use the oc create secret generic command with the --from-file option to create a Kubernetes secret.

Depending on the connection mode that is required by the ObjectServer, create a Secret with the required fields. The secret name should contain the helm release name as a prefix for easy reference.

Example commands are shown below for each connection mode using probe as the release name to create a secret called probe-omni-secret in the noi-integrations namespace.