Skip to content

Commit

Permalink
Merge pull request #35590 from ravisantoshgudimetla/dev-1.25
Browse files Browse the repository at this point in the history
Promote PodOS field to GA
  • Loading branch information
k8s-ci-robot authored Aug 17, 2022
2 parents a98137b + c8bedc8 commit 6b23f69
Show file tree
Hide file tree
Showing 3 changed files with 8 additions and 9 deletions.
5 changes: 2 additions & 3 deletions content/en/docs/concepts/windows/intro.md
Original file line number Diff line number Diff line change
Expand Up @@ -88,13 +88,12 @@ section refers to several key workload abstractions and how they map to Windows.
* OS field:

The `.spec.os.name` field should be set to `windows` to indicate that the current Pod uses Windows containers.
The `IdentifyPodOS` feature gate needs to be enabled for this field to be recognized.

{{< note >}}
Starting from 1.24, the `IdentifyPodOS` feature gate is in Beta stage and defaults to be enabled.
Starting from 1.25, the `IdentifyPodOS` feature gate is in GA stage and defaults to be enabled.
{{< /note >}}

If the `IdentifyPodOS` feature gate is enabled and you set the `.spec.os.name` field to `windows`,
If you set the `.spec.os.name` field to `windows`,
you must not set the following fields in the `.spec` of that Pod:

* `spec.hostPID`
Expand Down
7 changes: 3 additions & 4 deletions content/en/docs/concepts/windows/user-guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -158,14 +158,13 @@ schedule Linux and Windows workloads to their respective OS-specific nodes.
The recommended approach is outlined below,
with one of its main goals being that this approach should not break compatibility for existing Linux workloads.

If the `IdentifyPodOS` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) is
enabled, you can (and should) set `.spec.os.name` for a Pod to indicate the operating system
Starting from 1.25, you can (and should) set `.spec.os.name` for each Pod, to indicate the operating system
that the containers in that Pod are designed for. For Pods that run Linux containers, set
`.spec.os.name` to `linux`. For Pods that run Windows containers, set `.spec.os.name`
to Windows.
to `windows`.

{{< note >}}
Starting from 1.24, the `IdentifyPodOS` feature is in Beta stage and defaults to be enabled.
Starting from 1.25, the `IdentifyPodOS` feature is in GA stage and defaults to be enabled.
{{< /note >}}

The scheduler does not use the value of `.spec.os.name` when assigning Pods to nodes. You should
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -111,8 +111,6 @@ different Kubernetes components.
| `HonorPVReclaimPolicy` | `false` | Alpha | 1.23 | |
| `HPAContainerMetrics` | `false` | Alpha | 1.20 | |
| `HPAScaleToZero` | `false` | Alpha | 1.16 | |
| `IdentifyPodOS` | `false` | Alpha | 1.23 | 1.23 |
| `IdentifyPodOS` | `true` | Beta | 1.24 | |
| `InTreePluginAWSUnregister` | `false` | Alpha | 1.21 | |
| `InTreePluginAzureDiskUnregister` | `false` | Alpha | 1.21 | |
| `InTreePluginAzureFileUnregister` | `false` | Alpha | 1.21 | |
Expand Down Expand Up @@ -376,6 +374,9 @@ different Kubernetes components.
| `HugePages` | `true` | GA | 1.14 | - |
| `HyperVContainer` | `false` | Alpha | 1.10 | 1.19 |
| `HyperVContainer` | `false` | Deprecated | 1.20 | - |
| `IdentifyPodOS` | `false` | Alpha | 1.23 | 1.23 |
| `IdentifyPodOS` | `true` | Beta | 1.24 | 1.24 |
| `IdentifyPodOS` | `true` | GA | 1.25 | - |
| `IPv6DualStack` | `false` | Alpha | 1.15 | 1.20 |
| `IPv6DualStack` | `true` | Beta | 1.21 | 1.22 |
| `IPv6DualStack` | `true` | GA | 1.23 | - |
Expand Down

0 comments on commit 6b23f69

Please sign in to comment.