Issue

Kubernetes resources are not visible in the OpsRamp portal after installation.

Cause

• The OpsRamp master agent pod (example: opsramp-agent-master-xxxxx) is responsible for discovering Kubernetes objects and relationships. If it is not healthy, discovery will fail.
• The K8s-2.0 agent uses OpenTelemetry for data collection; delays may occur during initial processing.
• Resource data can take 5–10 minutes to sync and reflect on the OpsRamp portal.

Solution

1. Confirm the master agent pod is running:

   kubectl get pods -n opsramp-agent | grep master

2. Wait at least 5–10 minutes after installation for the initial discovery to complete.
3. Log in to the OpsRamp portal and verify discovered Kubernetes resources.
4. If discovery still fails:
   • Check the master agent pod logs for errors:

     kubectl logs <opsramp-agent-master-pod-name> -n opsramp-agent

   • Ensure the cluster has connectivity to the OpsRamp cloud endpoint.
   • Restart the master agent pod if it appears stuck:

     kubectl delete pod <opsramp-agent-master-pod-name> -n opsramp-agent