Kubernetes adapter authentication failing preventing data collection.

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• The  Kubernetes adapter status shows a Warning or Error.

• The following alerts are triggered in VCF Operations:

  • Adapter instance is not receiving data

  • Objects are not receiving data from adapter instance

• Validating the adapter connection may return a "null" error.

• The Kubernetes adapter logs, found at the path '/storage/vcops/logs/adapter/Kubernetes' may show errors similar to the error below;

• WARN  KubernetesAdapter ##### [ops@#### threadId="#####" threadName="pool-#####-thread-1" instanceId="#####"] [(#####) com.vmware.vcops.adapter.utils.CadvisorRestClient.performGetJson] - Api call to /api/v1/nodes/<FQDN>/proxy/api/v2.1/stats/ failed on https://<Control_Plane_IP>:6443. Exception - 503 - {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"error trying to reach service: dial tcp <Internal_IP>:PORT: connect: connection refused","reason":"ServiceUnavailable","code":503}

Environment

VCF Operations 9.0.x

Cause

This issue is caused by the unavailability or misconfiguration of the cAdvisor service on the target Kubernetes cluster.

Resolution

To resolve this issue, ensure that the cAdvisor service is correctly deployed and exposing the expected port on your Kubernetes cluster.

• Determine if you are running Red Hat OpenShift, VMware Tanzu, or upstream Kubernetes, as the configuration requirements may vary.

• Connect to your Kubernetes cluster and verify that the cAdvisor DaemonSet is deployed and the pods are in a Running state.

  • kubectl get daemonset -n <namespace>

• Check Port Configuration; Inspect the cAdvisor DaemonSet YAML definition. Ensure that the container port 31194 is exposed and mapped correctly to the host port.

  • Creating a cAdvisor YAML Definition

• Update VCF Operations Adapter Configuration

  • Log in to the VCF Operations user interface.

  • Navigate to Data Sources > Integrations.

  • Edit the Kubernetes adapter instance.

  • Ensure the cAdvisor Port field matches the port exposed in your DaemonSet YAML (31194).

  • Configuring Kubernetes Integration

• Click Validate Connection to confirm the adapter can now communicate with the cAdvisor service. Save the configuration once successful.