NSX Application Platform Node Disk Usage Very High Alarm is open
All NAPP Versions
Recommended actions:
In the NSX UI, navigate to System | NSX Application Platform and check the Storage field of individual nodes to see which node is under pressure.
1. Add one or more nodes to the K8s cluster. (Reach out to the k8s provider to add nodes to the existing cluster)
2. On the NSX Manager root shell:
napp-k get pods -o wide | grep <napp_node_name>
napp_node_name can be found from the open alarm
3. From the above list delete a few of the pods using "napp-k delete pod <pod-name>" command. These pods will now be scheduled on the new node.
Once the above steps are done, kubelet should eventually automatically free up unused container image space which in most cases will be the major contributor to disk space usage.
Recommended pods to delete if they are in the above list: cluster-api, monitor
Step to get cluster-api pod name on the NSX Manager root shell:
napp-k get pod -l=app.kubernetes.io/name=cluster-api
Step to get monitor pod name on the NSX Manager root shell:
napp-k get pod -l=app.kubernetes.io/name=monitor,cluster-api-client=true
If the above steps do not help, please contact your kubernetes service provider or VMware support for help clearing up disk space from the k8s nodes.