content: Fix typos in versions requirements for userns
The variable expansion is wrong: it currently expands to 1.27.3 on the rendered website, so it says it is supported in 1.27 and that it is not. Let's just re-work this paragraph so it is cleaerer and the variable expansion is what we want (1.27 and not 1.27.3)- Signed-off-by: Rodrigo Campos <rodrigoca@microsoft.com>pull/41906/head
parent
74ee1d9875
commit
0797a850da
|
@ -54,9 +54,13 @@ to use this feature with Kubernetes stateless pods:
|
||||||
|
|
||||||
* CRI-O: version 1.25 (and later) supports user namespaces for containers.
|
* CRI-O: version 1.25 (and later) supports user namespaces for containers.
|
||||||
|
|
||||||
Please note that containerd v1.7 supports user namespaces for containers,
|
containerd v1.7 is not compatible with the userns support in Kubernetes v{{< skew currentVersion >}}.
|
||||||
compatible with Kubernetes {{< skew currentPatchVersion >}}. It should not be used
|
Kubernetes v1.25 and v1.26 used an earlier implementation that **is** compatible with containerd v1.7,
|
||||||
with Kubernetes 1.27 (and later).
|
in terms of userns support.
|
||||||
|
If you are using a version of Kubernetes other than {{< skew currentVersion >}},
|
||||||
|
check the documentation for that version of Kubernetes for the most relevant information.
|
||||||
|
If there is a newer release of containerd than v1.7 available for use, also check the containerd
|
||||||
|
documentation for compatibility information.
|
||||||
|
|
||||||
Support for this in [cri-dockerd is not planned][CRI-dockerd-issue] yet.
|
Support for this in [cri-dockerd is not planned][CRI-dockerd-issue] yet.
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue