Skip to content

Commit

Permalink
Revise explanation for DefaultHostNetworkHostPortsInPodTemplates
Browse files Browse the repository at this point in the history
Co-authored-by: Antonio Ojea <[email protected]>
  • Loading branch information
sftim and aojea committed Feb 2, 2024
1 parent a5e512e commit 3b2873b
Showing 1 changed file with 8 additions and 5 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -10,9 +10,12 @@ stages:
defaultValue: false
fromVersion: "1.28"
---
Changes when the default value of
`PodSpec.containers[*].ports[*].hostPort`
is assigned. The default is to only set a default value in Pods.
This feature gate controls the point at which a default value for
`.spec.containers[*].ports[*].hostPort`
is assigned, for Pods using `hostNetwork: true`. The default since Kubernetes v1.28 is to only set a default
value in Pods.

Enabling this means a default will be assigned even to embedded
PodSpecs (e.g. in a Deployment), which is the historical default.
Enabling this means a default will be assigned even to the `.spec` of an embedded
[PodTemplate](/docs/concepts/workloads/pods/#pod-templates) (for example, in a Deployment),
which is the way that older releases of Kubernetes worked.
You should migrate your code so that it does not rely on the legacy behavior.

0 comments on commit 3b2873b

Please sign in to comment.