Explore Kubernetes clusters
The Kubernetes Clusters page provides visibility into all Kubernetes clusters connected to Cloud Security (InsightCloudSec). From this page, you can:
- Monitor cluster visibility and scanner status
- Resume or pause scanning
- Force a scan
- Access related Kubernetes resources
To view clusters:
- Enable Kubernetes Security Guardrails for your clusters.
- Navigate to Cloud > Kubernetes Clusters.
Fix missing runtime findings in Cloud Security
If runtime findings for a cluster do not appear in Cloud Security, the cluster is not fully configured for runtime security. No data is lost. You can still access runtime findings in Container Runtime Security. To restore visibility in Cloud Security, locate the clusters in Container Runtime Security and complete onboarding:
- Connect the associated cloud account for remote clusters
- Enable Kubernetes security guardrails for local clusters
Runtime findings will appear in Cloud Security after both features are enabled.
The Kubernetes Clusters page supports advanced filtering to help you narrow results and locate specific clusters quickly. Cluster status values:
| Status | Meaning |
|---|---|
| OK | Successfully harvested and enabled for scanning |
| Paused | Harvested but scanning is not enabled |
| Unauthorized | Permission or token issues prevent harvesting |
| Failed | Connectivity or scanning failure |
Review Enable and use Kubernetes Security Guardrails for more information on scans. If you want workload-level detail, you must Enable Container Runtime Security.
You can delete a cluster from this interface. This will remove it from view but does not remove it from the cloud provider. If a cluster is deleted outside of Cloud Security:
- It will be marked as deleted during the next harvesting cycle.
- Related Kubernetes entities will also be marked as deleted.
- The associated cloud account will remain in the interface.
- Harvesting state is set to Paused.