@olivierlambert Thank you so much. Got it.

Thinking this should be really easy to do so I'm probably missing something. Read most of the post about this and none of the links in those posts seem to work.

I've read the following:

https://xcp-ng.org/docs/guests.html#windows

..and understand the difference between Citrix and XCP-NG flavors and would like to install XCP-NG flavor so I'm clicking the installation link found from and it takes me here:

https://github.com/xcp-ng/win-pv-drivers/releases

From the above page, I'm unsure where to go next ?

I was thinking there would simply be a download option , with some zipped exe where I can simply click it from within the Windows VM and presto , have the tools installed (similar to VMWare ) or even how tools are installed for Linux VM's.

Having a super hard time getting out the gate on this one so any tips greatly appreciated!

Thank you so much

@BenjiReis , yes, all of the nodes could communicate with each other. The CIDR supplied in the template was in a different range which didn't overlap existing ones (i.e. completely different). This morning, I had to move forward so manually deployed a 10 node cluster (< what a pain! ) and had to abandon the template for now. I do plan to try this again as I'm certain I may have been doing something wrong and it would make my life easier if I can get it working. One thing I noticed this morning is the master was out of disk space and only 4 GB was allocated . Seems pretty low. I'll try again sometime.

New to K8s. Simply using the recipe to deploy a small 3 node cluster. Master and workers came up successfully and can ssh into each node using debian user and key. IPs are supplied to nodes via DHCP. From the master I can check the node status but <none> is specified for the ROLES of the workers:

$ kubectl get nodes
NAME     STATUS   ROLES    AGE   VERSION
master   Ready    master   22m   v1.19.2
node-1   Ready    <none>   15m   v1.19.2
node-2   Ready    <none>   15m   v1.19.2
node-3   Ready    <none>   15m   v1.19.2

Again, never used K8 before, but this doesn't seem right?

Next, I create a deployment:

debian@master:~$ kubectl create deployment kubernetes-bootcamp --image=gcr.io/google-samples/kubernetes-bootcamp:v1

deployment.apps/kubernetes-bootcamp created

Next, I verify , but available column shows 0

$ kubectl get deployments
NAME                  READY   UP-TO-DATE   AVAILABLE   AGE
kubernetes-bootcamp   0/1     1            0           14m

Pod is pending also:

$ kubectl get pods
NAME READY STATUS RESTARTS AGE
kubernetes-bootcamp-57978f5f5d-t6bsm 0/1 Pending 0 16m

I also see taints but unsure what's needed to resolve the issue:

$  kubectl describe pods
Name:           kubernetes-bootcamp-57978f5f5d-t6bsm
Namespace:      default
Priority:       0
Node:           <none>
Labels:         app=kubernetes-bootcamp
                pod-template-hash=57978f5f5d
Annotations:    <none>
Status:         Pending
IP:
IPs:            <none>
Controlled By:  ReplicaSet/kubernetes-bootcamp-57978f5f5d
Containers:
  kubernetes-bootcamp:
    Image:        gcr.io/google-samples/kubernetes-bootcamp:v1
    Port:         <none>
    Host Port:    <none>
    Environment:  <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-bqs24 (ro)
Conditions:
  Type           Status
  PodScheduled   False
Volumes:
  default-token-bqs24:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-bqs24
    Optional:    false
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  63s (x13 over 17m)  default-scheduler  0/4 nodes are available: 1 node(s) had taint {node-role.kubernetes.io/master: }, that the pod didn't tolerate, 3 node(s) had taint {node.kubernetes.io/disk-pressure: }, that the pod didn't tolerate.

Checking network interfaces I have the following (from the master)

# ip addr sh
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 02:a1:71:79:d0:1c brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.168/24 brd 192.168.1.255 scope global dynamic eth0
       valid_lft 4886sec preferred_lft 4886sec
    inet6 fe80::a1:71ff:fe79:d01c/64 scope link
       valid_lft forever preferred_lft forever
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:e5:e1:84:8a brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever
4: kube-bridge: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1480 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether ce:7d:de:2f:39:8b brd ff:ff:ff:ff:ff:ff
    inet6 fe80::cc7d:deff:fe2f:398b/64 scope link
       valid_lft forever preferred_lft forever

Kind of lost and not sure what to do next or how to resolve

Any tips greatly appreciated!

BTW - I absolutely love xcp-NG and XOA. One of the best switches I've made in a long time.