issue when creating vsphere pod

gcasale — Fri, 26 Aug 2022 07:40:43 GMT

I'm unable to create vsphere pod since there are no nodes available ; pod should run on a VM since it is a VM pod not on a cluster ;

The same error happens also when I try to deploy embedded harbor, that try to creates some vpshere pods inside dedicated registry namespace.

localuser@linux-jh-v7:~$ kubectl describe pod ubuntu
Name: ubuntu
Namespace: hcinsslab
Priority: 0
Node: <none>
Labels: app=ubuntu
Annotations: kubernetes.io/psp: wcp-default-psp
Status: Pending
IP:
IPs: <none>
Containers:
ubuntu:
Image: ubuntu:latest
Port: <none>
Host Port: <none>
Command:
/bin/sleep
3650d
Environment: <none>
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-kxt2j (ro)
Conditions:
Type Status
PodScheduled False
Volumes:
kube-api-access-kxt2j:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
ConfigMapOptional: <nil>
DownwardAPI: true
QoS Class: BestEffort
Node-Selectors: <none>
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning FailedScheduling 3d18h default-scheduler 0/3 nodes are available: 3 node(s) had taint {node-role.kubernetes.io/master: }, that the pod didn't tolerate.

Re: issue when creating vsphere pod

Digory34 — Tue, 06 Sep 2022 09:48:53 GMT

What is your command used to create your POD?

topic issue when creating vsphere pod in VMware vSphere™ Discussions

issue when creating vsphere pod

Re: issue when creating vsphere pod