Limitations of NetBackup deployment on AKS

Note the following limitations:

(Applicable only for media servers) A storage class that has the storage type as Azure file is not supported. When the Config-Checker runs the validation for checking the storage type, the Config-Checker job fails if it detects the storage type as Azure file. But if the Config-Checker is skipped then this validation is not run, and there can be issues in the deployment. There is no workaround available for this limitation. You must clean up the PVCs and CRs and reapply the CRs.
Only NFS is supported as the protocol while performing data migration with Azure premium files.
Media server scale down is not supported. Certain workloads that require media server affinity for the clients would not work.
External Certificate Authority (ECA) is not supported.
In case of load balancer service updating the CR with dynamic IP address to static IP address and vice versa is not allowed.
Media server pods as NetBackup storage targets are not supported. For example, NetBackup storage targets like AdvancedDisk and so on are not supported on the media server pods.
As per Microsoft, since the NFS file share is in Premium account, the minimum file share size is 100GB. If you create a PVC with a small storage size, the following error message is displayed:
"failed to create file share ... size (5)...".
The IP displayed is of POD IP. NetBackup installing on container takes the IP address of POD as configured IP. Even logs would have POD IP reference at many places.