Auto-deployment of the Kubernetes workload fails with time-out error
The auto deployment of the Kubernetes workload may fail if configuring the NetBackup Backup server certificate takes longer than the default 5 minute polling timeout.
The Backup Server Certificate setup might time out if the 'max open files' limit is set too high in the NetBackup Kubernetes Operator. In Kubernetes, containers get this limit from the container runtime (like Docker or containerd) on the node. When the limit is usually high, it can slow down the certificate configuration, causing it to exceed the default timeout.
To resolve this issue, reduce the max open files value to a reasonable level using the container runtime's configuration. Since Kubernetes does not manage this limit directly, you need to update the runtime settings on each cluster node. Post re-configuration, re-run the NetBackup Kubernetes auto deployment.
For more details, refer article.