From fe7771aeac323f2bd59490fdcf06e283eca67106 Mon Sep 17 00:00:00 2001 From: James Sturtevant Date: Thu, 15 Jul 2021 09:07:47 -0700 Subject: [PATCH] Remove annotation for Experimental Windows Hyper-v removed in 1.21: https://github.com/kubernetes/kubernetes/pull/95505 --- .../en/docs/reference/labels-annotations-taints.md | 12 ------------ 1 file changed, 12 deletions(-) diff --git a/content/en/docs/reference/labels-annotations-taints.md b/content/en/docs/reference/labels-annotations-taints.md index 29f3a63a8c..cd966f6150 100644 --- a/content/en/docs/reference/labels-annotations-taints.md +++ b/content/en/docs/reference/labels-annotations-taints.md @@ -200,18 +200,6 @@ 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 - -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. -{{< /note >}} - ## ingressclass.kubernetes.io/is-default-class Example: `ingressclass.kubernetes.io/is-default-class: "true"`