Notes for Load Balancer service

Note the following points:

After deployment of primary server or media server, updating the DNS name, IP address and subnet through CR is not allowed.
If mistakenly user has added wrong values:
- User wants to update IP address and subnet, you must delete the CR and update the CR yaml and reapply it.
- User wants to update the DNS name, you must delete the respective CR and delete the respective PVC and PV as well.
  Note:
  Be cautious while performing this step, this may lead to data loss.
Before using the DNS and its respective IP address in CR yaml, you can verify the IP address and its DNS resolution using nslookup.
In case of media server scaleout, ensure that the number of IP addresses mentioned in IPList in networkLoadBalancer section matches the replica count.
If nslookup is done for loadbalancer IP inside the container, it returns the DNS in the form of <svc name>.<namespace_name>.svc.cluster.local. This is Kubernetes behavior. Outside the pod, the loadbalancer service IP address is resolved to the configured DNS. The nbbptestconnection command inside the pods can provide a mismatch in DNS names, which can be ignored.