kubeadm_init_phase_etcd_local [page]deterministic
### Synopsis
Generate the static Pod manifest file for a local, single-node local etcd instance
``` kubeadm init phase etcd local [flags] ```
### Examples
``` # Generates the static Pod manifest file for etcd, functionally # equivalent to what is generated by kubeadm init. kubeadm init phase etcd local # Generates the static Pod manifest file for etcd using options # read from a configuration file. kubeadm init phase etcd local --config config.yaml ```
### Options
<table style="width: 100%; table-layout: fixed;"> <colgroup> <col span="1" style="width: 10px;" /> <col span="1" /> </colgroup> <tbody>
<tr> <td colspan="2">--cert-dir string Default: "/etc/kubernetes/pki"</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>The path where to save and store the certificates.</p></td> </tr>
<tr> <td colspan="2">--config string</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Path to a kubeadm configuration file.</p></td> </tr>
<tr> <td colspan="2">--dry-run</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Don't apply any changes; just output what would be done.</p></td> </tr>
<tr> <td colspan="2">-h, --help</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>help for local</p></td> </tr>
<tr> <td colspan="2">--image-repository string Default: "registry.k8s.io"</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Choose a container registry to pull control plane images from</p></td> </tr>
<tr> <td colspan="2">--patches string</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Path to a directory that contains files named "target[suffix][+patchtype].extension". For example, "kube-apiserver0+merge.yaml" or just "etcd.json". "target" can be one of "kube-apiserver", "kube-controller-manager", "kube-scheduler", "etcd", "kubeletconfiguration", "corednsdeployment". "patchtype" can be one of "strategic", "merge" or "json" and they match the patch formats supported by kubectl. The default "patchtype" is "strategic". "extension" must be either "json" or "yaml". "suffix" is an optional string that can be used to determine which patches are applied first alpha-numerically.</p></td> </tr>
</tbody> </table>
### Options inherited from parent commands
<table style="width: 100%; table-layout: fixed;"> <colgroup> <col span="1" style="width: 10px;" /> <col span="1" /> </colgroup> <tbody>
<tr> <td colspan="2">--rootfs string</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path.</p></td> </tr>
</tbody> </table>