Make it clear that Knative doesn't limit the use of different Kubernetes runtimes

[csantanapr]

Feedback from CNCF TOC member Emily Fox during CNCF due diligence review.

Emily Fox - KCCN Co-Chair Today at 10:14 AM @dims - Do you know if knative has any plans to extend Knative Functions (in development) to leverage some form of container isolation or be compatible with it? I don't see any references to this in their issues or DD doc, however i did come across #12533 (recently opened) to explore true multi-tenancy.

Emily Fox 23 minutes ago Thanks all for the discussion, I’d love to see some of this referenced in the existing docs to ensure users are aware that there are not limitations in this regard.

We could add in the docs some information to make users aware that there is no limitations on terms of Kuberentes runtime, that they can use any runtime supported by the Kubernetes cluster they install Knative. The user can configure this in their Knative Service annotation https://deploy-preview-4715--knative.netlify.app/development/serving/configuration/feature-flags/#kubernetes-runtime-class

apiVersion: serving.knative.dev/v1
kind: Service
...
spec:
  template:
    spec:
      runtimeClassName: myclass
...

This will set the runtimeClassName on the Pod to be created.

Maybe we add a sentence under Serving or maybe a blog post on how to configure a runtime and use it in Knative for example "gvisor"

[github-actions[bot]]

This issue is stale because it has been open for 90 days with no activity. It will automatically close after 30 more days of inactivity. Reopen the issue with /reopen. Mark the issue as fresh by adding the comment /remove-lifecycle stale.

[abrennan89]

It looks like this was asked specifically wrt Functions, so it would be dependent IMO on https://github.com/knative/docs/issues/5038 and the outcome of SC discussions about how Functions is marketed, how it fits into our docs overall etc. Marking as blocked for now until this information is available.

[knative-prow-robot]

This issue or pull request is stale because it has been open for 90 days with no activity.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close

/lifecycle stale

[github-actions[bot]]

This issue is stale because it has been open for 90 days with no activity. It will automatically close after 30 more days of inactivity. Reopen the issue with /reopen. Mark the issue as fresh by adding the comment /remove-lifecycle stale.