After installing primary server CR

Note the following points:

(AKS-specific) The primary server CR will create a pod, a statefulset, a load balancer service, a configmap, a persistent volume claim for log volume, and a persistent volume claim for catalog volume.
(EKS-specific) The primary server CR will create a pod, a statefulset, a load balancer service, a configmap and PVCs.
Primary server can be considered as successfully installed and running when log-viewer, nbatd, nbmqbroker, nbwsapp, bpdbm, policyjob, policyjobmgr, primary, requestrouter pods successfully got into running state.
You can access the NetBackup Web UI using the primary server hostname that was specified in the primary server CR status in Primary server details section.
For example, if the primary server hostname is nbu-primary, then you can access the Web UI at https://nbu-primary/webui/login.
Check the installation progress in the pod logs by using the following command:
kubectl logs <request-router-pod-name> -n <namespace>
Request router can be considered as successfully installed and running when the request router pod's state is ready (1/1).