Integration profile
Discovery provider · Kubernetes
Discover clusters, namespaces, workloads, services, nodes, and ingress resources.
Demo baseline · November 13, 2026Prerequisites
- Kubernetes API access from a collector or workload identity
- Least-privilege ClusterRole and binding
- Trusted cluster CA certificate
Configuration steps
- Choose the authentication method
- Bind the read-only ClusterRole
- Select namespaces and resource kinds
- Validate the API and preview discovery
Provider fields
| Field | Type | Requirement and options |
|---|---|---|
Kubernetes API serverapiServerUrl | url | Required |
Authentication modeauthMode | select | Requiredworkload_identity, service_account_token, kubeconfig, client_certificate |
Kubeconfig / token secret aliaskubeconfigSecretAlias | text | Optional |
Cluster namesclusterNames | tag_list | Required |
Included namespacesnamespaces | tag_list | Optional |
Excluded namespacesexcludedNamespaces | tag_list | Optional |
Resource kindsresourceKinds | tag_list | Optional |
Collector / MID servercollector | text | Optional |
Validate cluster certificatevalidateTls | boolean | Optional |
Verify and troubleshoot
Test with the narrowest supported non-production scope. Confirm that the connection test reaches the expected provider and that the preview or receipt matches the intended scope. Check identity, credential references, network access and provider permissions before retrying. Record the failure stage and redact sensitive payloads when escalating.