-
Notifications
You must be signed in to change notification settings - Fork 531
Open
Labels
Description
What happened?
When deploying kind, then vcluster, then interlink (which deploys a virtual kubelet), the virtual node from interlink is deleted by vcluster.
What did you expect to happen?
The virtual node appears when doing kubectl get node
.
How can we reproduce it (as minimally and precisely as possible)?
- deploy kind 0.19.0
- deploy vcluster 0.18.1 or 0.19.4
- deploy interlink core component (see https://intertwin-eu.github.io/interLink/docs/tutorial-admins/deploy-interlink)
Anything else we need to know?
See https://github.com/interTwin-eu/interLink/issues/260
This error pattern appears in vcluster logs:
delete virtual node my-vk-node, because it is not needed anymore
Which means vcluster deletes it. The code from vcluster is at https://github.com/loft-sh/vcluster/blob/v0.19.4/pkg/controllers/resources/nodes/syncer.go#L271 , at SyncToHost . I think vcluster thinks of the virtual kubelet as one of its own virtual node, and deletes it because it does not recognize it.
Host cluster Kubernetes version
$ kubectl version
Client Version: v1.28.2
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.29.0
vcluster version
0.18.1 and 0.19.4
VCluster Config
# My vcluster.yaml / values.yaml here