The media server CR will create a pod, a configmap, a loadbalancer service, a persistent volume claim for data volume, and a persistent volume claim for log volume.

Initially pod will be in not ready state (0/2) when installation is going in the background. Check the pod logs for installation progress using the following command:

kubectl logs <media-pod-name> -n <namespace>

Media server can be considered as successfully installed and running when the media server pod's state is ready (2/2).

Details of media server name for each replica can be obtained from media server CR status by running the following command:

kubectl describe <MediaServer_cr_name> -n <namespace>