"Error from server (workload management cluster uses vSphere Networking, which does not support action on kind Pod)" when trying to deploy a workload inside the Supervisor Cluster.
Article ID: 377351
Updated On:
Products
Issue/Introduction
1. When attempting to deploy a workload via kubectl, you get the error message "Error from server (workload management cluster uses vSphere Networking, which does not support action on kind Pod)"
2. All the kubectl apply -f commands fail with the same error.
3. vSphere with Tanzu is configured to use vSphere Networking (vDS).
4. The issue is observed when the workload creation is attempted directly on the namespace which belongs to the Supervisor Cluster and not inside any Guest Cluster namespace.
Environment
vSphere with Tanzu
VMware vCenter Server
Cause
vSphere with Tanzu networking on vDS does not support deploying Workloads on Supervisor as ESXi hosts do not act as Worker Nodes.
Resolution
1. Create an additional Tanzu Guest Cluster inside the supervisor namespace which will deploy its own Control Plane VMs and Worker VMs. The workloads can then be deployed on the top of the same.
2. Once the Guest Cluster is created, use the below command to login to the newly created Tanzu Guest cluster, to start deploying workloads:
kubectl vsphere login --server=SUPERVISOR-CLUSTER-CONTROL-PLANE-IP --tanzu-kubernetes-cluster-name TANZU-KUBERNETES-CLUSTER-NAME --tanzu-kubernetes-cluster-namespace SUPERVISOR-NAMESPACE-WHERE-THE-CLUSTER-IS-DEPLOYED --vsphere-username VCENTER-SSO-USER-NAME
Additional Information
Connect to a Tanzu Kubernetes Cluster as a vCenter Single Sign-On User
https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere-supervisor/7-0/vsphere-with-tanzu-configuration-and-management-7-0.html
Document for creating Tanzu Guest Cluster as per the requirements:
http://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere-supervisor/7-0/vsphere-with-tanzu-configuration-and-management-7-0.html
Feedback
