You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/aks/use-windows-hpc.md
+2-5Lines changed: 2 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Use Windows HostProcess containers
3
3
description: Learn how to use HostProcess & Privileged containers for Windows workloads on AKS
4
4
ms.topic: article
5
-
ms.date: 4/6/2022
5
+
ms.date: 05/09/2023
6
6
ms.author: juda
7
7
8
8
---
@@ -13,7 +13,6 @@ HostProcess / Privileged containers extend the Windows container model to enable
13
13
14
14
A privileged DaemonSet can carry out changes or monitor a Linux host on Kubernetes but not Windows hosts. HostProcess containers are the Windows equivalent of host elevation.
15
15
16
-
17
16
## Limitations
18
17
19
18
* HostProcess containers require Kubernetes 1.23 or greater.
@@ -26,7 +25,6 @@ A privileged DaemonSet can carry out changes or monitor a Linux host on Kubernet
26
25
* Resource limits such as disk, memory, and cpu count, work the same way as fashion as processes on the host.
27
26
* Named pipe mounts and Unix domain sockets aren't directly supported, but can be accessed on their host path, for example `\\.\pipe\*`.
28
27
29
-
30
28
## Run a HostProcess workload
31
29
32
30
To use HostProcess features with your deployment, set *hostProcess: true* and *hostNetwork: true*:
For more information on HostProcess containers and Microsoft's contribution to Kubernetes upstream, see the [Alpha in v1.22: Windows HostProcess Containers][blog-post].
0 commit comments