Merge pull request #34159 from neolit123/1.25-update-unversioned-kubelet-config-map-fg-info

kubeadm: update unversioned kubelet config map fg info
This commit is contained in:
Kubernetes Prow Robot
2022-07-10 18:31:47 -07:00
committed by GitHub
@@ -147,15 +147,15 @@ directly to kubeadm is not supported. Instead, it is possible to pass them by
List of feature gates: List of feature gates:
{{< table caption="kubeadm feature gates" >}} {{< table caption="kubeadm feature gates" >}}
Feature | Default | Alpha | Beta Feature | Default | Alpha | Beta | GA
:-------|:--------|:------|:----- :-------|:--------|:------|:-----|:----
`PublicKeysECDSA` | `false` | 1.19 | - `PublicKeysECDSA` | `false` | 1.19 | - | -
`RootlessControlPlane` | `false` | 1.22 | - `RootlessControlPlane` | `false` | 1.22 | - | -
`UnversionedKubeletConfigMap` | `true` | 1.22 | 1.23 `UnversionedKubeletConfigMap` | `true` | 1.22 | 1.23 | 1.25
{{< /table >}} {{< /table >}}
{{< note >}} {{< note >}}
Once a feature gate goes GA it is removed from this list as its value becomes locked to `true` by default. Once a feature gate goes GA its value becomes locked to `true` by default.
{{< /note >}} {{< /note >}}
Feature gate descriptions: Feature gate descriptions:
@@ -181,10 +181,6 @@ or `kubeadm upgrade apply`), kubeadm respects the value of `UnversionedKubeletCo
(during `kubeadm join`, `kubeadm reset`, `kubeadm upgrade ...`), kubeadm attempts to use unversioned ConfigMap name first; (during `kubeadm join`, `kubeadm reset`, `kubeadm upgrade ...`), kubeadm attempts to use unversioned ConfigMap name first;
if that does not succeed, kubeadm falls back to using the legacy (versioned) name for that ConfigMap. if that does not succeed, kubeadm falls back to using the legacy (versioned) name for that ConfigMap.
{{< note >}}
Setting `UnversionedKubeletConfigMap` to `false` is supported but **deprecated**.
{{< /note >}}
### Adding kube-proxy parameters {#kube-proxy} ### Adding kube-proxy parameters {#kube-proxy}
For information about kube-proxy parameters in the kubeadm configuration see: For information about kube-proxy parameters in the kubeadm configuration see: