Suggestion: Kata deployment scripts should check that nested virtualization is enabled about cloud-native-setup HOT 8 OPEN

@olberger since the script itself runs only on master, maybe updating https://github.com/kata-containers/packaging/tree/master/kata-deploy is a better idea?

In this repo we could add all examples to make use of node-selector with kata-runtime true label. That way they wont land on nodes that do not support kata-runtime class. This is a workaround for the current limitation in runtimeclass.

cc @egernst @mcastelino

from cloud-native-setup.

@olberger thanks for the suggestion!

from cloud-native-setup.

@egernst does your kata-deploy script check for this today?

from cloud-native-setup.

no

from cloud-native-setup.

We should see if we can use NFD to detect support for VT-x and use that as part of kata-deploy when available.

/cc @krsna1729

from cloud-native-setup.

@mcastelino that will only save a daemonset pod. It doesnt solve the problem of scheduling the actual workload itself

from cloud-native-setup.

that will only save a daemonset pod. It doesnt solve the problem of scheduling the actual workload itself

True but AFAICS the limitation comes from RuntimeClass that assumes homogeneous cluster.

from cloud-native-setup.

Yes see second comment

from cloud-native-setup.