diff options
| author | Ian Lewis <ianlewis@google.com> | 2018-12-10 22:56:19 -0800 |
|---|---|---|
| committer | Shentubot <shentubot@google.com> | 2018-12-10 22:57:14 -0800 |
| commit | 93ac04a6c32003597b3c639480126f8048988b72 (patch) | |
| tree | 750a1738f25d5f670e48e7173b044b1c86a0d7a5 | |
| parent | 52fe3b87a415006a4ef96548e33a7153b14ac28d (diff) | |
Minor wording update to Kubernetes support section of the README
Updated the README to correct some wording and clarify a bit that containerd
CRI runtime is needed.
PiperOrigin-RevId: 224944753
Change-Id: I7b9c527500f99571aca7ef73058472ae9b3d5371
| -rw-r--r-- | README.md | 3 |
1 files changed, 2 insertions, 1 deletions
@@ -236,7 +236,8 @@ the gVisor addon is enabled, pods with `io.kubernetes.cri.untrusted-workload` set to true will execute with `runsc`. Follow [these instructions][minikube] to enable gVisor addon. -You can also setup Kubernetes node to use `gvisor-containerd-shim`. Pods with +You can also setup Kubernetes nodes to run pods in gvisor using the `containerd` +CRI runtime and the `gvisor-containerd-shim`. Pods with the `io.kubernetes.cri.untrusted-workload` annotation will execute with `runsc`. You can find instructions [here][gvisor-containerd-shim]. |