kata sample admission controller: Move to kata repository about cloud-native-setup HOT 5 CLOSED

Adding a comment here since I am unable to create an issue at the forked repo -

We should coordinate with kata-deploy labels and add nodeSelector field to the pod spec, to get scheduled only on nodes with kata installed.

We should also add these labels in our kubeadm.yaml file.

from cloud-native-setup.

Actually on second thought, assuming a homogeneous Clear cluster, all nodes would be capable of running kata runtimeClass. So we may not need the labels and nodeSelector. WDYT?

/cc @egernst

from cloud-native-setup.

@mcastelino

This needs to be moved to a kata specific repository and hosted under the kata dockerhub.

If this is the end goal, then the webhook should use kata-deploy labels and stick a nodeselctor.

Our setup should either install kata using kata-deploy (redundant since we have pkgs) or add same labels to nodes on bootstrap

from cloud-native-setup.

Personally, I'd like to see this under Kata, as this is very kata + k8s specific, and distro agnostic.

from cloud-native-setup.

Resolved-by: kata-containers/tests#1080

from cloud-native-setup.