From 7145fb89d6a5fcbc40c86d6d9eca6d3d3b702ae3 Mon Sep 17 00:00:00 2001 From: James Sturtevant Date: Thu, 22 Jul 2021 11:12:20 -0700 Subject: [PATCH] address feedback --- .../en/docs/reference/labels-annotations-taints.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/content/en/docs/reference/labels-annotations-taints.md b/content/en/docs/reference/labels-annotations-taints.md index cd966f6150..bb36561997 100644 --- a/content/en/docs/reference/labels-annotations-taints.md +++ b/content/en/docs/reference/labels-annotations-taints.md @@ -200,6 +200,19 @@ Used on: Service The kube-proxy has this label for custom proxy, which delegates service control to custom proxy. +## experimental.windows.kubernetes.io/isolation-type (deprecated) + +Example: `experimental.windows.kubernetes.io/isolation-type: "hyperv"` + +Used on: Pod + +The annotation is used to run Windows containers with Hyper-V isolation. To use Hyper-V isolation feature and create a Hyper-V isolated container, the kubelet should be started with feature gates HyperVContainer=true and the Pod should include the annotation experimental.windows.kubernetes.io/isolation-type=hyperv. + +{{< note >}} +You can only set this annotation on Pods that have a single container. +Starting in v1.20, this annotation is deprecated as experimental hyper-v support was removed in 1.21. +{{< /note >}} + ## ingressclass.kubernetes.io/is-default-class Example: `ingressclass.kubernetes.io/is-default-class: "true"`