Kubernetes has launched kubeadm v1.31, signaling a significant shift to the v1beta4 configuration format. The previous v1beta3 format is now deprecated, with support scheduled for removal after three minor releases.
The v1beta4 format brings several enhancements and features. Key changes include:
- Two new configuration elements: ResetConfiguration and UpgradeConfiguration.
- InitConfiguration and JoinConfiguration now offer a dryRun mode.
- A new field, nodeRegistration.imagePullSerial, manages image pull behavior during node registration.
In ClusterConfiguration, users will find new fields like:
- certificateValidityPeriod
- caCertificateValidityPeriod
- encryptionAlgorithm
- dns.disabled
- proxy.disabled
These additions increase kubeadm’s flexibility by allowing users to control CoreDNS and kube-proxy addons during cluster setup.
Noteworthy updates consist of:
- A structured method for extra arguments in the configuration, accommodating duplicates.
- The introduction of a timeouts structure for various kubeadm operations.
Users can also utilize the kubeadm config migrate command to transition effortlessly from v1beta3 to v1beta4 formats.
To gain a deeper understanding of the changes and migration steps, users should consult the official Kubernetes documentation.
