Error: Unable to reach tca service from ingress. Please check the status of the service by accessing the cluster

search cancel

book

calendar_today

VMware Telco Cloud Platform VMware Telco Cloud Automation

Users are unable to access the VMware Telco Cloud Automation Control Plane (TCA-CP) web interface on port 9443.
The browser displays the error: "Unable to reach tca service from ingress. Please check the status of the service by accessing the cluster".
Pods in the tca-cp-cn namespace (e.g., tca-api, tca-app) are in CrashLoopBackOff or Error status.
Attempts to run kubectl logs fail with Error from server ("log" not found).
The partition /dev/mapper/vg_logs-lv_logs is at 100% utilization.

The /logs partition on the Telco Cloud Automation Control Plane (TCA-CP) appliance has reached 100% capacity.
When the log disk is full, the Kubelet cannot create the necessary log pipes or metadata files for container execution, causing pods to fail during initialization.
This is frequently caused by a large accumulation of historical logs in the /logs/retained-logs directory.

Verify the disk space usage:
df -h /logs
Identify large historical log files within the retained logs directory:
find /logs/retained-logs -type f -size +50M
Navigate to the directories containing the largest files (typically associated with the tca-cp-cn pods) and remove older log rotations.
cd /logs/retained-logs/k8s.tca-cp-cn.tca-app-<ID>/
rm tca.2025*
cd kubelet.service/
rm kubelet.2025*
Verify that space has been reclaimed (utilization should ideally be below 80%):
df -h /logs
Wait several minutes for the Kubernetes scheduler to automatically restart the pods. Verify pod status:
kubectl get pods -n tca-cp-cn
Verify the Telco Cloud Automation Control Plane (TCA-CP) is reachable via the web browser and showing as "Connected" in the TCA Manager UI.

Patch TCA Nodes as this is a known issue for more details. See the following KB for more details.
Fix: Cronjob failure in airgap environment

thumb_up Yes

thumb_down No