Virtual Kubelet: Controller Integration

[MbolotSuse]

Currently the Virtual Kubelet must be deployed on it's own after the K3k cluster has been deployed. This is a poor and complicated user experience. The K3k controller should deploy the virtual kubelet and ensure that it registers to form a working virtual cluster without intervention from the user. The following requirements should be met:

• The K3k kubelet should be deployed automatically when the node type is set to shared
• The shared node type should be the default
• When the node type is shared, the server should be deployed in agentless mode
• When the node type is shared, no agents should be deployed (or permitted to be deployed)
• The k3k kubelet should be configured with the minimum permissions necessary in the host cluster
• The k3k kubelet should automatically register with the host cluster