kubeadm Configuration (v1beta4) [page]deterministic
<h2>Overview</h2> <p>Package v1beta4 defines the v1beta4 version of the kubeadm configuration file format. This version improves on the v1beta3 format by fixing some minor issues and adding a few new fields.</p> <p>A list of changes since v1beta3:</p> <p>v1.35:</p> <ul> <li>Add <code>httpEndpoints</code> field to <code>ClusterConfiguration.etcd.externalEtcd</code> that can be used to configure the HTTP endpoints for etcd communication in v1beta4. This field is used to separate the HTTP traffic (such as <code>/metrics</code> and <code>/health</code> endpoints) from the gRPC traffic handled by <code>endpoints</code>. This separation allows for better access control, as HTTP endpoints can be exposed without exposing the primary gRPC interface. Corresponds to etcd's <code>--listen-client-http-urls</code> configuration. If not provided, <code>endpoints</code> will be used for both gRPC and HTTP traffic.</li> </ul> <p>v1.34:</p> <ul> <li>Add "ECDSA-P384" to the allowed encryption algorithm options for <code>ClusterConfiguration.encryptionAlgorithm</code>.</li> </ul> <p>v1.33:</p> <ul> <li>Add an <code>EtcdUpgrade</code> field to <code>UpgradeConfiguration.plan</code> that can be used to control whether the etcd upgrade plan should be displayed.</li> </ul> <p>v1.31:</p> <ul> <li>Support custom environment variables in control plane components under <code>ClusterConfiguration</code>. Use <code>apiServer.extraEnvs</code>, <code>controllerManager.extraEnvs</code>, <code>scheduler.extraEnvs</code>, <code>etcd.local.extraEnvs</code>.</li> <li>The <code>ResetConfiguration</code> API type is now supported in v1beta4. Users are able to reset a node by passing a <code>--config</code> file to <code>kubeadm reset</code>.</li> <li>Dry run mode is now configureable in <code>InitConfiguration</code> and <code>JoinConfiguration</code>B.</li> <li>Replace the existing string/string extra argument maps with structured extra arguments that support duplicates. The change applies to <code>ClusterConfiguration</code> - <code>apiServer.extraArgs</code>, <code>controllerManager.extraArgs</code>, <code>scheduler.extraArgs</code>, <code>etcd.local.extraArgs</code>. Also to <code>nodeRegistration.kubeletExtraArgs</code>.</li> <li>Add <code>ClusterConfiguration.encryptionAlgorithm</code> that can be used to set the asymmetric encryption algorithm used for this cluster's keys and certificates. Can be one of <code>"RSA-2048"</code> (default), <code>"RSA-3072"</code>, <code>"RSA-4096"</code> or <code>"ECDSA-P256"</code>.</li> <li>Add <code>ClusterConfiguration.dns.disabled</code> and <code>ClusterConfiguration.proxy.disabled</code> that can be used to disable the CoreDNS and kube-proxy addons during cluster initialization. Skipping the related addons phases, during cluster creation will set the same fields to <code>true</code>.</li> <li>Add the <code>nodeRegistration.imagePullSerial</code> field in <code>InitConfiguration</code> and <code>JoinConfiguration</code>, which can be used to control if kubeadm pulls images serially or in parallel.</li> <li>The <code>UpgradeConfiguration</code> kubeadm API is now supported in v1beta4 when passing <code>--config</code> to <code>kubeadm upgrade</code> subcommands. Usage of component configuration for <code>kubelet</code> and <code>kube-proxy</code>, <code>InitConfiguration</code> and <code>ClusterConfiguration</code> is deprecated and will be ignored when passing <code>--config</code> to <code>upgrade</code> subcommands.</li> <li>Add a <code>Timeouts</code> structure to <code>InitConfiguration</code>, <code>JoinConfiguration</code>, <code>ResetConfiguration</code> and <code>UpgradeConfiguration</code> that can be used to configure various timeouts. The <code>ClusterConfiguration.timeoutForControlPlane</code> field is replaced by <code>Timeouts.controlPlaneComponentHealthCheck</code>. The <code>JoinConfiguration.discovery.timeout</code> is replaced by <code>timeouts.Discovery …(trimmed)