Add support of hyperv isolation for windows containers #58750
Closed
Description
Is this a BUG REPORT or FEATURE REQUEST?:
This is needed for:
- running Windows Server 2016 containers on Windows Server 1709
- providing a stronger isolation boundary between pods. This is important for scenarios where you need to host pods for multiple tenants or security levels on the same node
Proposal is to use an annotation, not an API change: windows.kubernetes.io/isolation-type=hyperv
Uncomment only one, leave it on its own line:
/kind bug
/kind feature
What happened:
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
- Kubernetes version (use
kubectl version
): - Cloud provider or hardware configuration:
- OS (e.g. from /etc/os-release):
- Kernel (e.g.
uname -a
): - Install tools:
- Others: