Kubernetes Cluster

Integrate a self‑managed Kubernetes cluster with Cloudaware to inventory cluster resources for unified operational reporting.

info

• Audience: Cloudaware administrators, platform engineers
• Outcome: Self-managed Kubernetes clusters, such as on-prem or privately hosted clusters, are connected to Cloudaware and cluster/workload objects are continuously discovered in the CMDB

Capabilities

The integration supports:

• Read-only discovery of core cluster resources (namespaces, nodes, pods, services, etc.)
• Workload correlation with Applications and related cluster assets
• Search, reporting, and coverage analysis for self-managed Kubernetes objects

Prerequisites

Before you begin, make sure you have:

• Access to a Cloudaware account.
• A user with access to the Admin Console and permissions to manage cloud accounts, organizations, and integrations (Cloudaware Administrator).
• Cluster URL reachable from Cloudaware (public) or via TunHub (private)
• One of:
  • Service Account token with cluster‑wide read (view) + nodes list/watch
  • Client certificate signed by the cluster CA

Add a Kubernetes Cluster to Cloudaware

1. In Cloudaware, open Admin → Integrations → Kubernetes Cluster → + ADD.
2. Provide Cluster URL and either a Service Account token or client certificate details.
3. For private clusters, set up TunHub and use its URL/port.
4. Save and confirm Status turns green.

View Kubernetes Cluster Data in CMDB

To browse discovered Kubernetes Cluster resources:

1. In Cloudaware, open CMDB Navigator.
2. In the left pane, select KUBERNETES.
3. Open Kubernetes Clusters to view connected clusters.
4. Open related object lists, e.g., Kubernetes Cluster Nodes, to review records.

Use CMDB list views and reports to filter Kubernetes objects by cluster, namespace, workload, label, or owner.

Supported Objects

Cloudaware supports the following Kubernetes Cluster objects:

Kubernetes Object	CMDB Object API Name
Kubernetes Cluster	CA10K__CaKubernetesCluster__c
Kubernetes Cluster Config Map	CA10K__CaKubernetesClusterConfigMap__c
Kubernetes Cluster Daemon Set	CA10K__CaKubernetesClusterDaemonSet__c
Kubernetes Cluster Deployment	CA10K__CaKubernetesClusterDeployment__c
Kubernetes Cluster Endpoint	CA10K__CaKubernetesClusterEndpoint__c
Kubernetes Cluster HPA	CA10K__CaKubernetesClusterHpa__c
Kubernetes Cluster Ingress	CA10K__CaKubernetesClusterIngress__c
Kubernetes Cluster Limit Range	CA10K__CaKubernetesClusterLimitRange__c
Kubernetes Cluster Namespace	CA10K__CaKubernetesClusterNamespace__c
Kubernetes Cluster Network Policy	CA10K__CaKubernetesClusterNetworkPolicy__c
Kubernetes Cluster Network Policy Rule	CA10K__CaKubernetesClusterNetworkPolicyRule__c
Kubernetes Cluster Node	CA10K__CaKubernetesClusterNode__c
Kubernetes Cluster Node Address	CA10K__CaKubernetesClusterNodeAddress__c
Kubernetes Cluster Pod	CA10K__CaKubernetesClusterPod__c
Kubernetes Cluster Pod Container	CA10K__CaKubernetesClusterPodContainer__c
Kubernetes Cluster Pod Disruption Budget	CA10K__CaKubernetesClusterPodDisruptionBudget__c
Kubernetes Cluster Replica Set	CA10K__CaKubernetesClusterReplicaSet__c
Kubernetes Cluster Resource Quota	CA10K__CaKubernetesClusterResourceQuota__c
Kubernetes Cluster Role	CA10K__CaKubernetesClusterRole__c
Kubernetes Cluster Role Binding	CA10K__CaKubernetesClusterRoleBinding__c
Kubernetes Cluster Secret	CA10K__CaKubernetesClusterSecret__c
Kubernetes Cluster Service	CA10K__CaKubernetesClusterService__c
Kubernetes Cluster Service Account	CA10K__CaKubernetesClusterServiceAccount__c
Kubernetes Cluster Service Account Secret	CA10K__CaKubernetesClusterServiceAccSecret__c
Kubernetes Cluster Stateful Set	CA10K__CaKubernetesClusterStatefulSet__c
Kubernetes Cluster Storage Class	CA10K__CaKubernetesClusterStorageClass__c

Troubleshooting

note

Initial discovery can take time after the integration status turns green.

RBAC Denied or Some Objects Are Missing

• Confirm the Service Account, user, or client certificate identity has read access at cluster scope.
• Ensure the identity can list and watch core workload objects.
• If node records are missing, verify that node list and watch permissions are explicitly granted.
• Recheck the ClusterRole and ClusterRoleBinding subject. The namespace and service account name must match the token used in the Cloudaware integration.

Certificate or TLS Errors

• Verify that the Kubernetes API URL uses the correct hostname and port.
• Confirm that the certificate authority data matches the CA that signed the Kubernetes API server certificate.
• If the API endpoint uses a private or self-signed certificate, confirm that the certificate chain is trusted by the integration configuration.
• If certificate-based authentication continues to fail, use a Service Account token to isolate whether the issue is TLS trust or client certificate authentication.

Integration Status Is Red or the Connection Check Fails

• Confirm that the Kubernetes API endpoint is reachable from Cloudaware or through the configured private connectivity path.
• Verify that the Cluster URL has the correct protocol, hostname, and port.
• Re-enter the token or certificate values and save the integration again.
• Check whether network firewalls, allowlists, security groups, or ingress rules block the Kubernetes API endpoint.

Private Cluster Is Not Reachable

• Route private network access through TunHub.
• Confirm that the TunHub URL and port in the Kubernetes Cluster integration match the private Kubernetes API endpoint mapping.
• Verify that the TunHub gateway can reach the Kubernetes API endpoint from inside the private network.

Data Does Not Appear in CMDB

• Allow the initial discovery cycle to complete.
• In CMDB Navigator, verify that you are viewing the KUBERNETES section and related object lists.
• Confirm that the integration status remains green after saving.
• If only some objects are missing, review RBAC permissions for the affected object type.

Security Notes

• Use read-only RBAC (view) plus required node permissions.
• Rotate tokens/certificates regularly.

Related

• TunHub