Skip to content

Include Pod OS field #35985

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
k8s-ci-robot merged 2 commits into from
Aug 22, 2022
Merged

Include Pod OS field #35985

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5206c7f
Include Pod OS field
ravisantoshgudimetla Aug 15, 2022
84da6bb
Fix broken shortcode
Aug 22, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions content/en/docs/concepts/workloads/pods/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -138,6 +138,23 @@ it is deleted.
When you create the manifest for a Pod object, make sure the name specified is a valid
[DNS subdomain name](/docs/concepts/overview/working-with-objects/names#dns-subdomain-names).

### Pod OS

{{< feature-state state="stable" for_k8s_version="v1.25" >}}

You should set the `.spec.os.name` field to either `windows` or `linux` to indicate the OS on
Copy link
Contributor

@marosset marosset Aug 15, 2022 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit:
Should this be 'To indicate the OS on which the pod is intended to run on, set the .spec.os.name field to either windows or linux. ?
This avoids language like should or can.

Copy link
Contributor

@sftim sftim Aug 16, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like that we're making a recommendation. It's more than “there's this field, you could use it if you like”; now the field is GA, it's “you ought to set this field”.

If we had the capacity it'd be nice to show a sample webhook that produces a Warning when you don't set that for a Pod / pod template.

Copy link
Contributor

@sftim sftim Aug 16, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given that there's System.Net.HttpListener, that sample webhook could even be written in PowerShell!

Copy link
Contributor Author

@ravisantoshgudimetla ravisantoshgudimetla Aug 16, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we had the capacity it'd be nice to show a sample webhook that produces a Warning when you don't set that for a Pod / pod template.

We can do that but it is left to the user as an exercise since the use-cases may differ.

which you want the pod to run. These two are the only operating systems supported for now by
Kubernetes. In future, this list may be expanded.

In Kubernetes v{{< skew currentVersion >}}, the value you set for this field has no
effect on {{< glossary_tooltip text="scheduling" term_id="kube-scheduler" >}} of the pods.
Setting the `.spec.os.name` helps to identify the pod OS
authoratitively and is used for validation. The kubelet refuses to run a Pod where you have
specified a Pod OS, if this isn't the same as the operating system for the node where
that kubelet is running.
The [Pod security standards](/docs/concepts/security/pod-security-standards/) also use this
field to avoid enforcing policies that aren't relevant to that operating system.

### Pods and controllers

You can use workload resources to create and manage multiple Pods for you. A controller
Expand Down