Support runtimeClass feature

[gnmahanth]

What would you like to be added:
Support Kubernetes runtimeClass feature
(https://kubernetes.io/docs/concepts/containers/runtime-class/)

Why is this needed:
If there is a need to test untrusted workload having a runtime like gvisor, ignite or kata will be helpful.
Since kind already have containerd as CRI and it can support multiple runtime through containerd plugins.

[BenTheElder]

Ignite and kata are not going to work well inside the kind nodes (kvm being a non-containerized resource that we'd leak), though we'd like to use them as a backend for kind's nodes possibly at some point.

runsc in the default ptrace mode would actually probably be fine though 🤔

We'd have to look into the overhead.

[aojea]

For reference

https://github.com/gnmahanth/kind-runsc

thanks @gnmahanth , awesome work documenting it

[BenTheElder]

revisiting this in the next cycle.

[BenTheElder]

One issue is:

gVisor builds on x86_64 and ARM64. Other architectures may become available in the future.

But Kubernetes supports more than this.

And in the install docs only x86_64 https://gvisor.dev/docs/user_guide/install/

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[BenTheElder]

Technically runtimeClass is supported, but we don't ship any special runtimeclasses¹.

We're opting not to ship non-standard extensions otherwise at this time.

Footnotes

1. We actually have to ship one "test" runtime class for testing Kubernetes, it is actually the same as the "normal" runtimeClass. ↩