This will be fixed in Telco Cloud Automation 3.0
Workaround:
As a workaround user needs to switch to the right cluster context using the following steps:
1. SSH to the TCA-CP/bootstrapper VM as admin
2. Switch to root user.
3. Use kubectl command below to query for all the cluster contexts.
kubectl config get-contexts
4. Switch to the desired cluster context using the command below.
kubectl config use-context context_name
5. Verify context switch operation by querying for k8s resources available within the cluster.
kubectl get api-resource-name -n namespace" / "kubectl get api-resource-name -A