1.30 Release Notes: "Known Issues"

[rashansmith]

What happened?

This issue is a bucket placeholder for collaborating on the "Known Issues" additions for the 1.30 Release Notes. If you know of issues or API changes that are going out in 1.30, please comment here so that we can coordinate incorporating information about these changes in the Release Notes.

/assign @kubernetes/release-team-release-notes

/sig release
/milestone v1.30

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[npolshakova]

kubernetes/release#3516

[neolit123]

we have two regressions in kubeadm for 1.30.0.
please adjust the language or format as see fit.

---

Kubeadm 1.30.0 includes two regressions related to the kubeadm upgrade apply command. The kubeadm maintainers recommend that you skip 1.30.0 and upgrade to 1.30.1 instead, or alternatively apply the mitigations explained below.

• kubeadm upgrade apply fails with a CreateJob preflight error if the cluster has a single node that is a control plane node.
  upgrade-health-check Job fails on a single control plane node cluster after drain kubeadm#3050
  To mitigate the problem, you can pass the flag --ignore-preflight-errors=CreateJob

• kubeadm upgrade apply does not download the KubeletConfiguration stored in the cluster in the kube-system/kubelet-config ConfigMap and instead writes a file with defaults in /var/lib/kubelet/config.yaml.
  kubeadm upgrade apply v1.30.0 loses custom kubelet configuration kubeadm#3049
  To mitigate the problem, you have to manually get the ConfigMap contents with kubectl get cm -n kube-system kubelet-config -o "jsonpath={.data['kubelet']}", write them to /var/lib/kubelet/config.yaml and manually apply any node-specific customizations if you are using --patches with a kubeletconfiguration target.

[carlory]

@neolit123 links are incorrect.

[neolit123]

@neolit123 links are incorrect.

fixed

[pmalek]

• 1.30 adds tags that break imagePullSecrets #124540 users including ImagePullSecrets or in their CRDs will not be able to apply them using kubernetes packages from 1.30.0 tag
  • fix backported to release-1.30 branch in [backport release-1.30]: fix(api): make LocalObjectReference.Name and HostAlias.IP required (#124553) #124694.