Ensure that the Identity Reporting database is created with proper privileges (by default, postgres user as owner for Identity Reporting database) and is accessible from the Identity Reporting container running remotely on Kubernetes worker node.
Log in to the Kubernetes master node.
Copy the secret.properties file and the Identity Reporting Tomcat keystore (tomcat-rpt.ks) into the data volume path that you specified during the configuration. For example, /data.
Run the following command to deploy the container:
kubectl create -f <location of the YAML file>
For example:
kubectl create -f /data/Reporting_AE.yaml
To verify whether the pod was successfully deployed, check the log file by running the following command:
kubectl exec <pod> -- /usr/bin/tail -f /var/opt/netiq/idm/log/idmconfigure.log
For example,
kubectl exec identityreporting -- /usr/bin/tail -f /var/opt/netiq/idm/log/idmconfigure.log
(Conditional) Run the following command to verify the status of the deployed pod:
kubectl get pods -o=wide
To check the details of the deployed pod, run the following command:
kubectl describe pod <pod name>
For example,
kubectl describe pod identityreporting
To log in to the pod, run the following command:
kubectl exec -it <pod name> -- /bin/bash
For example,
kubectl exec -it identityreporting -- /bin/bash
Run the following command:
NOTE:Before performing this step, ensure that the container is deployed successfully.
/opt/netiq/common/jre/bin/keytool -importkeystore -srckeystore /config/tomcat-osp.ks -srcstorepass <password> -destkeystore /opt/netiq/idm/apps/tomcat/conf/idm.jks -deststorepass <password>
Run the following command to exit the container.
exit
Restart the pod using the following command:
docker restart identityreporting