Skip to content
Closed
Changes from all commits
Commits
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
Original file line number Diff line number Diff line change
Expand Up @@ -129,6 +129,7 @@ For a reference to old feature gates that are removed, please refer to
| `KMSv2KDF` | `false` | Beta | 1.28 | |
| `KubeProxyDrainingTerminatingNodes` | `false` | Alpha | 1.28 | |
| `KubeletCgroupDriverFromCRI` | `false` | Alpha | 1.28 | |
| `KubeletEnsureSecretPulledImages` | `false` | Alpha | 1.29 | |
Copy link
Contributor

Choose a reason for hiding this comment

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

Each and every gate needs a description that can be found at the end of this file, in alphabeta order.

| `KubeletInUserNamespace` | `false` | Alpha | 1.22 | |
| `KubeletPodResourcesDynamicResources` | `false` | Alpha | 1.27 | |
| `KubeletPodResourcesGet` | `false` | Alpha | 1.27 | |
Expand Down Expand Up @@ -584,6 +585,12 @@ Each feature gate is designed for enabling/disabling a specific feature:
the `cgroupDriver` configuration setting.
See [Configuring a cgroup driver](/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver)
for more details.
- `KubeletEnsureSecretPulledImages`: add support in kubelet for the `pullIfNotPresent`
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- `KubeletEnsureSecretPulledImages`: add support in kubelet for the `pullIfNotPresent`
- `KubeletEnsureSecretPulledImages`: change the behavior of the `IfNotPresent`

image pull policy, for ensuring images pulled with pod `imagePullSecrets` are re-authenticated
for other pods that do not have the same `imagePullSecret`/auths used to successfully pull
the images in the first place.
Comment on lines +590 to +591
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
for other pods that do not have the same `imagePullSecret`/auths used to successfully pull
the images in the first place.
for other pods that do not have the same `imagePullSecret` authentication information that was used
to retrieve that Pod's container image(s) in the first place.

This policy change will have no affect on the pull always image pull policy or for images
that are preloaded.
Comment on lines +592 to +593
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
This policy change will have no affect on the pull always image pull policy or for images
that are preloaded.
Enabling this feature gate has no effect on Pods that use the `Always` image pull policy, nor for the
`Never` image pull policy or for container images that are preloaded onto the target node.

- `KubeletInUserNamespace`: Enables support for running kubelet in a
{{<glossary_tooltip text="user namespace" term_id="userns">}}.
See [Running Kubernetes Node Components as a Non-root User](/docs/tasks/administer-cluster/kubelet-in-userns/).
Expand Down