Remove .orig and _backup_ files (#15011)

* remove all .orig files

* remove all backup files

* remove base, local and remote backup files

content/en/docs/concepts/workloads/controllers/daemonset.md.orig

@@ -1,246 +0,0 @@
----
-reviewers:
-- enisoc
-- erictune
-- foxish
-- janetkuo
-- kow3ns
-title: DaemonSet
-content_template: templates/concept
-weight: 50
----
-
-{{% capture overview %}}
-
-A _DaemonSet_ ensures that all (or some) Nodes run a copy of a Pod.  As nodes are added to the
-cluster, Pods are added to them.  As nodes are removed from the cluster, those Pods are garbage
-collected.  Deleting a DaemonSet will clean up the Pods it created.
-
-Some typical uses of a DaemonSet are:
-
-- running a cluster storage daemon, such as `glusterd`, `ceph`, on each node.
-- running a logs collection daemon on every node, such as `fluentd` or `logstash`.
-- running a node monitoring daemon on every node, such as [Prometheus Node Exporter](https://github.com/prometheus/node_exporter), [Sysdig Agent](https://sysdigdocs.atlassian.net/wiki/spaces/Platform), `collectd`, [Dynatrace OneAgent](https://www.dynatrace.com/technologies/kubernetes-monitoring/), [AppDynamics Agent](https://docs.appdynamics.com/display/CLOUD/Container+Visibility+with+Kubernetes), [Datadog agent](https://docs.datadoghq.com/agent/kubernetes/daemonset_setup/), [New Relic agent](https://docs.newrelic.com/docs/integrations/kubernetes-integration/installation/kubernetes-installation-configuration), Ganglia `gmond` or [Instana Agent](https://www.instana.com/supported-integrations/kubernetes-monitoring/).
-
-In a simple case, one DaemonSet, covering all nodes, would be used for each type of daemon.
-A more complex setup might use multiple DaemonSets for a single type of daemon, but with
-different flags and/or different memory and cpu requests for different hardware types.
-
-{{% /capture %}}
-
-
-{{% capture body %}}
-
-## Writing a DaemonSet Spec
-
-### Create a DaemonSet
-
-You can describe a DaemonSet in a YAML file. For example, the `daemonset.yaml` file below describes a DaemonSet that runs the fluentd-elasticsearch Docker image:
-
-{{< codenew file="controllers/daemonset.yaml" >}}
-
-* Create a DaemonSet based on the YAML file:
-```
-kubectl apply -f https://k8s.io/examples/controllers/daemonset.yaml
-```
-
-### Required Fields
-
-As with all other Kubernetes config, a DaemonSet needs `apiVersion`, `kind`, and `metadata` fields.  For
-general information about working with config files, see [deploying applications](/docs/user-guide/deploying-applications/),
-[configuring containers](/docs/tasks/), and [object management using kubectl](/docs/concepts/overview/working-with-objects/object-management/) documents.
-
-A DaemonSet also needs a [`.spec`](https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status) section.
-
-### Pod Template
-
-The `.spec.template` is one of the required fields in `.spec`.
-
-The `.spec.template` is a [pod template](/docs/concepts/workloads/pods/pod-overview/#pod-templates). It has exactly the same schema as a [Pod](/docs/concepts/workloads/pods/pod/), except it is nested and does not have an `apiVersion` or `kind`.
-
-In addition to required fields for a Pod, a Pod template in a DaemonSet has to specify appropriate
-labels (see [pod selector](#pod-selector)).
-
-A Pod Template in a DaemonSet must have a [`RestartPolicy`](/docs/user-guide/pod-states)
- equal to `Always`, or be unspecified, which defaults to `Always`.
-
-### Pod Selector
-
-The `.spec.selector` field is a pod selector.  It works the same as the `.spec.selector` of
-a [Job](/docs/concepts/jobs/run-to-completion-finite-workloads/).
-
-As of Kubernetes 1.8, you must specify a pod selector that matches the labels of the
-`.spec.template`. The pod selector will no longer be defaulted when left empty. Selector
-defaulting was not compatible with `kubectl apply`. Also, once a DaemonSet is created,
-its `.spec.selector` can not be mutated. Mutating the pod selector can lead to the
-unintentional orphaning of Pods, and it was found to be confusing to users.
-
-The `.spec.selector` is an object consisting of two fields:
-
-* `matchLabels` - works the same as the `.spec.selector` of a [ReplicationController](/docs/concepts/workloads/controllers/replicationcontroller/).
-* `matchExpressions` - allows to build more sophisticated selectors by specifying key,
-  list of values and an operator that relates the key and values.
-
-When the two are specified the result is ANDed.
-
-If the `.spec.selector` is specified, it must match the `.spec.template.metadata.labels`. Config with these not matching will be rejected by the API.
-
-Also you should not normally create any Pods whose labels match this selector, either directly, via
-another DaemonSet, or via other controller such as ReplicaSet.  Otherwise, the DaemonSet
-controller will think that those Pods were created by it.  Kubernetes will not stop you from doing
-this.  One case where you might want to do this is manually create a Pod with a different value on
-a node for testing.
-
-### Running Pods on Only Some Nodes
-
-If you specify a `.spec.template.spec.nodeSelector`, then the DaemonSet controller will
-create Pods on nodes which match that [node
-selector](/docs/concepts/configuration/assign-pod-node/). Likewise if you specify a `.spec.template.spec.affinity`,
-then DaemonSet controller will create Pods on nodes which match that [node affinity](/docs/concepts/configuration/assign-pod-node/).
-If you do not specify either, then the DaemonSet controller will create Pods on all nodes.
-
-## How Daemon Pods are Scheduled
-
-### Scheduled by DaemonSet controller (disabled by default since 1.12)
-
-Normally, the machine that a Pod runs on is selected by the Kubernetes scheduler. However, Pods
-created by the DaemonSet controller have the machine already selected (`.spec.nodeName` is specified
-when the Pod is created, so it is ignored by the scheduler).  Therefore:
-
- - The [`unschedulable`](/docs/admin/node/#manual-node-administration) field of a node is not respected
-   by the DaemonSet controller.
- - The DaemonSet controller can make Pods even when the scheduler has not been started, which can help cluster
-   bootstrap.
-
-
-### Scheduled by default scheduler (enabled by default since 1.12)
-
-{{< feature-state state="beta" for-kubernetes-version="1.12" >}}
-
-A DaemonSet ensures that all eligible nodes run a copy of a Pod. Normally, the
-node that a Pod runs on is selected by the Kubernetes scheduler. However,
-DaemonSet pods are created and scheduled by the DaemonSet controller instead.
-That introduces the following issues:
-
- * Inconsistent Pod behavior: Normal Pods waiting to be scheduled are created
-   and in `Pending` state, but DaemonSet pods are not created in `Pending`
-   state. This is confusing to the user.
- * [Pod preemption](/docs/concepts/configuration/pod-priority-preemption/)
-   is handled by default scheduler. When preemption is enabled, the DaemonSet controller
-   will make scheduling decisions without considering pod priority and preemption.
-
-`ScheduleDaemonSetPods` allows you to schedule DaemonSets using the default
-scheduler instead of the DaemonSet controller, by adding the `NodeAffinity` term
-to the DaemonSet pods, instead of the `.spec.nodeName` term. The default
-scheduler is then used to bind the pod to the target host. If node affinity of
-the DaemonSet pod already exists, it is replaced. The DaemonSet controller only
-performs these operations when creating or modifying DaemonSet pods, and no
-changes are made to the `spec.template` of the DaemonSet.
-
-```yaml
-nodeAffinity:
-  requiredDuringSchedulingIgnoredDuringExecution:
-    nodeSelectorTerms:
-    - matchFields:
-      - key: metadata.name
-        operator: In
-        values:
-        - target-host-name
-```
-
-In addition, `node.kubernetes.io/unschedulable:NoSchedule` toleration is added
-automatically to DaemonSet Pods. The default scheduler ignores
-`unschedulable` Nodes when scheduling DaemonSet Pods.
-
-
-### Taints and Tolerations
-
-Although Daemon Pods respect
-[taints and tolerations](/docs/concepts/configuration/taint-and-toleration),
-the following tolerations are added to DaemonSet Pods automatically according to
-the related features.
-
-| Toleration Key                           | Effect     | Version | Description                                                  |
-| ---------------------------------------- | ---------- | ------- | ------------------------------------------------------------ |
-| `node.kubernetes.io/not-ready`           | NoExecute  | 1.13+    | DaemonSet pods will not be evicted when there are node problems such as a network partition. |
-| `node.kubernetes.io/unreachable`         | NoExecute  | 1.13+    | DaemonSet pods will not be evicted when there are node problems such as a network partition. |
-| `node.kubernetes.io/disk-pressure`       | NoSchedule | 1.8+    |                                                              |
-| `node.kubernetes.io/memory-pressure`     | NoSchedule | 1.8+    |                                                              |
-| `node.kubernetes.io/unschedulable`       | NoSchedule | 1.12+   | DaemonSet pods tolerate unschedulable attributes by default scheduler.                                                    |
-| `node.kubernetes.io/network-unavailable` | NoSchedule | 1.12+   | DaemonSet pods, who uses host network, tolerate network-unavailable attributes by default scheduler.                      |
-
-
-
-
-## Communicating with Daemon Pods
-
-Some possible patterns for communicating with Pods in a DaemonSet are:
-
-- **Push**: Pods in the DaemonSet are configured to send updates to another service, such
-  as a stats database.  They do not have clients.
-- **NodeIP and Known Port**: Pods in the DaemonSet can use a `hostPort`, so that the pods are reachable via the node IPs.  Clients know the list of node IPs somehow, and know the port by convention.
-- **DNS**: Create a [headless service](/docs/concepts/services-networking/service/#headless-services) with the same pod selector,
-  and then discover DaemonSets using the `endpoints` resource or retrieve multiple A records from
-  DNS.
-- **Service**: Create a service with the same Pod selector, and use the service to reach a
-  daemon on a random node. (No way to reach specific node.)
-
-## Updating a DaemonSet
-
-If node labels are changed, the DaemonSet will promptly add Pods to newly matching nodes and delete
-Pods from newly not-matching nodes.
-
-You can modify the Pods that a DaemonSet creates.  However, Pods do not allow all
-fields to be updated.  Also, the DaemonSet controller will use the original template the next
-time a node (even with the same name) is created.
-
-
-You can delete a DaemonSet.  If you specify `--cascade=false` with `kubectl`, then the Pods
-will be left on the nodes.  You can then create a new DaemonSet with a different template.
-The new DaemonSet with the different template will recognize all the existing Pods as having
-matching labels.  It will not modify or delete them despite a mismatch in the Pod template.
-You will need to force new Pod creation by deleting the Pod or deleting the node.
-
-In Kubernetes version 1.6 and later, you can [perform a rolling update](/docs/tasks/manage-daemon/update-daemon-set/) on a DaemonSet.
-
-## Alternatives to DaemonSet
-
-### Init Scripts
-
-It is certainly possible to run daemon processes by directly starting them on a node (e.g. using
-`init`, `upstartd`, or `systemd`).  This is perfectly fine.  However, there are several advantages to
-running such processes via a DaemonSet:
-
-- Ability to monitor and manage logs for daemons in the same way as applications.
-- Same config language and tools (e.g. Pod templates, `kubectl`) for daemons and applications.
-- Running daemons in containers with resource limits increases isolation between daemons from app
-  containers.  However, this can also be accomplished by running the daemons in a container but not in a Pod
-  (e.g. start directly via Docker).
-
-### Bare Pods
-
-It is possible to create Pods directly which specify a particular node to run on.  However,
-a DaemonSet replaces Pods that are deleted or terminated for any reason, such as in the case of
-node failure or disruptive node maintenance, such as a kernel upgrade. For this reason, you should
-use a DaemonSet rather than creating individual Pods.
-
-### Static Pods
-
-It is possible to create Pods by writing a file to a certain directory watched by Kubelet.  These
-are called [static pods](/docs/concepts/cluster-administration/static-pod/).
-Unlike DaemonSet, static Pods cannot be managed with kubectl
-or other Kubernetes API clients.  Static Pods do not depend on the apiserver, making them useful
-in cluster bootstrapping cases.  Also, static Pods may be deprecated in the future.
-
-### Deployments
-
-DaemonSets are similar to [Deployments](/docs/concepts/workloads/controllers/deployment/) in that
-they both create Pods, and those Pods have processes which are not expected to terminate (e.g. web servers,
-storage servers).
-
-Use a Deployment for stateless services, like frontends, where scaling up and down the
-number of replicas and rolling out updates are more important than controlling exactly which host
-the Pod runs on.  Use a DaemonSet when it is important that a copy of a Pod always run on
-all or certain hosts, and when it needs to start before other Pods.
-
-{{% /capture %}}

content/en/docs/reference/command-line-tools-reference/feature-gates.md.orig

@@ -1,342 +0,0 @@
----
-title: Feature Gates
-weight: 10
-title: Feature Gates
-content_template: templates/concept
----
-
-{{% capture overview %}}
-This page contains an overview of the various feature gates an administrator
-can specify on different Kubernetes components.
-{{% /capture %}}
-
-{{% capture body %}}
-## Overview
-
-Feature gates are a set of key=value pairs that describe alpha or experimental
-features.
-An administrator can use the `--feature-gates` command line flag on each component
-to turn a feature on or off. Each component supports a set of feature gates unique to that component.
-Use `-h` flag to see a full set of feature gates for all components.
-To set feature gates for a component, such as kubelet, use the `--feature-gates` flag assigned to a list of feature pairs:
-
-```shell
---feature-gates="...,DynamicKubeletConfig=true"
-```
-
-The following table is a summary of the feature gates that you can set on
-different Kubernetes components.
-
-- The "Since" column contains the Kubernetes release when a feature is introduced
-  or its release stage is changed.
-- The "Until" column, if not empty, contains the last Kubernetes release in which
-  you can still use a feature gate.
-
-| Feature | Default | Stage | Since | Until |
-|---------|---------|-------|-------|-------|
-| `Accelerators` | `false` | Alpha | 1.6 | 1.10 |
-| `AdvancedAuditing` | `false` | Alpha | 1.7 | 1.7 |
-| `AdvancedAuditing` | `true` | Beta | 1.8 | 1.11 |
-| `AdvancedAuditing` | `true` | GA | 1.12 | - |
-| `AffinityInAnnotations` | `false` | Alpha | 1.6 | 1.7 |
-| `AllowExtTrafficLocalEndpoints` | `false` | Beta | 1.4 | 1.6 |
-| `AllowExtTrafficLocalEndpoints` | `true` | GA | 1.7 | - |
-| `APIListChunking` | `false` | Alpha | 1.8 | 1.8 |
-| `APIListChunking` | `true` | Beta | 1.9 | |
-| `APIResponseCompression` | `false` | Alpha | 1.7 | |
-| `AppArmor` | `true` | Beta | 1.4 | |
-| `AttachVolumeLimit` | `true` | Alpha | 1.11 | 1.11 |
-| `AttachVolumeLimit` | `true` | Beta | 1.12 | |
-| `BlockVolume` | `false` | Alpha | 1.9 | |
-| `BlockVolume` | `true` | Beta | 1.13 | - |
-| `BoundServiceAccountTokenVolume` | `false` | Alpha | 1.13 | |
-| `CPUManager` | `false` | Alpha | 1.8 | 1.9 |
-| `CPUManager` | `true` | Beta | 1.10 | |
-| `CRIContainerLogRotation` | `false` | Alpha | 1.10 | 1.10 |
-| `CRIContainerLogRotation` | `true` | Beta| 1.11 | |
-| `CSIBlockVolume` | `false` | Alpha | 1.11 | 1.13 |
-| `CSIBlockVolume` | `true` | Beta | 1.14 | |
-| `CSIDriverRegistry` | `false` | Alpha | 1.12 | 1.13 |
-| `CSIDriverRegistry` | `true` | Beta | 1.14 | |
-| `CSIInlineVolume` | `false` | Alpha | 1.15 | - |
-| `CSIMigration` | `false` | Alpha | 1.14 | |
-| `CSIMigrationAWS` | `false` | Alpha | 1.14 | |
-| `CSIMigrationAzureDisk` | `false` | Alpha | 1.15 | |
-| `CSIMigrationAzureFile` | `false` | Alpha | 1.15 | |
-| `CSIMigrationGCE` | `false` | Alpha | 1.14 | |
-| `CSIMigrationOpenStack` | `false` | Alpha | 1.14 | |
-| `CSINodeInfo` | `false` | Alpha | 1.12 | 1.13 |
-| `CSINodeInfo` | `true` | Beta | 1.14 | |
-| `CSIPersistentVolume` | `false` | Alpha | 1.9 | 1.9 |
-| `CSIPersistentVolume` | `true` | Beta | 1.10 | 1.12 |
-| `CSIPersistentVolume` | `true` | GA | 1.13 | - |
-| `CustomCPUCFSQuotaPeriod` | `false` | Alpha | 1.12 | |
-| `CustomPodDNS` | `false` | Alpha | 1.9 | 1.9 |
-| `CustomPodDNS` | `true` | Beta| 1.10 | |
-| `CustomResourceSubresources` | `false` | Alpha | 1.10 | 1.11 |
-| `CustomResourceSubresources` | `true` | Beta | 1.11 | - |
-| `CustomResourceValidation` | `false` | Alpha | 1.8 | 1.8 |
-| `CustomResourceValidation` | `true` | Beta | 1.9 | |
-| `CustomResourceWebhookConversion` | `false` | Alpha | 1.13 | |
-| `DebugContainers` | `false` | Alpha | 1.10 | |
-| `DevicePlugins` | `false` | Alpha | 1.8 | 1.9 |
-| `DevicePlugins` | `true` | Beta | 1.10 | |
-| `DryRun` | `true` | Beta | 1.13 | |
-| `DynamicAuditing` | `false` | Alpha | 1.13 | |
-| `DynamicKubeletConfig` | `false` | Alpha | 1.4 | 1.10 |
-| `DynamicKubeletConfig` | `true` | Beta | 1.11 | |
-| `DynamicProvisioningScheduling` | `false` | Alpha | 1.11 | 1.11 |
-| `DynamicVolumeProvisioning` | `true` | Alpha | 1.3 | 1.7 |
-| `DynamicVolumeProvisioning` | `true` | GA | 1.8 | |
-| `EnableEquivalenceClassCache` | `false` | Alpha | 1.8 | |
-| `ExpandCSIVolumes` | `false` | Alpha | 1.14 | | |
-| `ExpandInUsePersistentVolumes` | `false` | Alpha | 1.11 | 1.13 | |
-| `ExpandPersistentVolumes` | `false` | Alpha | 1.8 | 1.10 |
-| `ExpandPersistentVolumes` | `true` | Beta | 1.11 | |
-| `ExperimentalCriticalPodAnnotation` | `false` | Alpha | 1.5 | |
-| `ExperimentalHostUserNamespaceDefaulting` | `false` | Beta | 1.5 | |
-| `GCERegionalPersistentDisk` | `true` | Beta | 1.10 | 1.12 |
-| `GCERegionalPersistentDisk` | `true` | GA | 1.13 | - |
-| `HugePages` | `false` | Alpha | 1.8 | 1.9 |
-| `HugePages` | `true` | Beta| 1.10 | 1.13 |
-| `HugePages` | `true` | GA | 1.14 | |
-| `HyperVContainer` | `false` | Alpha | 1.10 | |
-| `Initializers` | `false` | Alpha | 1.7 | 1.13 |
-| `Initializers` | - | Deprecated | 1.14 | |
-| `KubeletConfigFile` | `false` | Alpha | 1.8 | 1.9 |
-| `KubeletPluginsWatcher` | `false` | Alpha | 1.11 | 1.11 |
-| `KubeletPluginsWatcher` | `true` | Beta | 1.12 | 1.12 |
-| `KubeletPluginsWatcher` | `true` | GA | 1.13 | - |
-| `KubeletPodResources` | `false` | Alpha | 1.13 | |
-| `LocalStorageCapacityIsolation` | `false` | Alpha | 1.7 | 1.9 |
-| `LocalStorageCapacityIsolation` | `true` | Beta| 1.10 | |
-| `LocalStorageCapacityIsolationFSQuotaMonitoring` | `false` | Alpha| 1.15 | |
-| `MountContainers` | `false` | Alpha | 1.9 | |
-| `MountPropagation` | `false` | Alpha | 1.8 | 1.9 |
-| `MountPropagation` | `true` | Beta | 1.10 | 1.11 |
-| `MountPropagation` | `true` | GA | 1.12 | |
-| `NodeLease` | `false` | Alpha | 1.12 | 1.13 |
-| `NodeLease` | `true` | Beta | 1.14 | |
-| `PersistentLocalVolumes` | `false` | Alpha | 1.7 | 1.9 |
-| `PersistentLocalVolumes` | `true` | Beta | 1.10 | 1.13 |
-| `PersistentLocalVolumes` | `true` | GA | 1.14 | |
-| `PodPriority` | `false` | Alpha | 1.8 | 1.10 |
-| `PodPriority` | `true` | Beta | 1.11 | 1.13 |
-| `PodPriority` | `true` | GA | 1.14 | |
-| `PodReadinessGates` | `false` | Alpha | 1.11 | |
-| `PodReadinessGates` | `true` | Beta | 1.12 | |
-| `PodShareProcessNamespace` | `false` | Alpha | 1.10 | |
-| `PodShareProcessNamespace` | `true` | Beta | 1.12 | |
-| `ProcMountType` | `false` | Alpha | 1.12 | |
-| `PVCProtection` | `false` | Alpha | 1.9 | 1.9 |
-| `ResourceLimitsPriorityFunction` | `false` | Alpha | 1.9 | |
-| `ResourceQuotaScopeSelectors` | `false` | Alpha | 1.11 | 1.11 |
-| `ResourceQuotaScopeSelectors` | `true` | Beta | 1.12 | |
-| `RotateKubeletClientCertificate` | `true` | Beta | 1.8 | |
-| `RotateKubeletServerCertificate` | `false` | Alpha | 1.7 | 1.11 |
-| `RotateKubeletServerCertificate` | `true` | Beta | 1.12 | |
-| `RunAsGroup` | `true` | Beta | 1.14 | |
-| `RuntimeClass` | `true` | Beta | 1.14 | |
-| `SCTPSupport` | `false` | Alpha | 1.12 | |
-| `ServerSideApply` | `false` | Alpha | 1.14 | |
-| `ServiceNodeExclusion` | `false` | Alpha | 1.8 | |
-| `StorageObjectInUseProtection` | `true` | Beta | 1.10 | 1.10 |
-| `StorageObjectInUseProtection` | `true` | GA | 1.11 | |
-| `StreamingProxyRedirects` | `true` | Beta | 1.5 | |
-| `SupportIPVSProxyMode` | `false` | Alpha | 1.8 | 1.8 |
-| `SupportIPVSProxyMode` | `false` | Beta | 1.9 | 1.9 |
-| `SupportIPVSProxyMode` | `true` | Beta | 1.10 | 1.10 |
-| `SupportIPVSProxyMode` | `true` | GA | 1.11 | |
-| `SupportPodPidsLimit` | `false` | Alpha | 1.10 | 1.13 |
-| `SupportPodPidsLimit` | `true` | Beta | 1.14 | |
-| `Sysctls` | `true` | Beta | 1.11 | |
-| `TaintBasedEvictions` | `false` | Alpha | 1.6 | 1.12 |
-| `TaintBasedEvictions` | `true` | Beta | 1.13 | |
-| `TaintNodesByCondition` | `false` | Alpha | 1.8 | 1.11 |
-| `TaintNodesByCondition` | `true` | Beta | 1.12 | |
-| `TokenRequest` | `false` | Alpha | 1.10 | 1.11 |
-| `TokenRequest` | `true` | Beta | 1.12 | |
-| `TokenRequestProjection` | `false` | Alpha | 1.11 | 1.11 |
-| `TokenRequestProjection` | `true` | Beta | 1.12 | |
-| `TTLAfterFinished` | `false` | Alpha | 1.12 | |
-| `VolumeScheduling` | `false` | Alpha | 1.9 | 1.9 |
-| `VolumeScheduling` | `true` | Beta | 1.10 | 1.12 |
-| `VolumeScheduling` | `true` | GA | 1.13 | |
-| `VolumeSubpathEnvExpansion` | `false` | Alpha | 1.14 | 1.14 |
-| `VolumeSubpathEnvExpansion` | `true` | Beta | 1.15 | |
-| `VolumeSnapshotDataSource` | `false` | Alpha | 1.12 | - |
-| `ScheduleDaemonSetPods` | `false` | Alpha | 1.11 | 1.11 |
-| `ScheduleDaemonSetPods` | `true` | Beta | 1.12 | |
-| `WindowsGMSA` | `false` | Alpha | 1.14 | |
-
-## Using a Feature
-
-### Feature Stages
-
-A feature can be in *Alpha*, *Beta* or *GA* stage.
-An *Alpha* feature means:
-
-* Disabled by default.
-* Might be buggy. Enabling the feature may expose bugs.
-* Support for feature may be dropped at any time without notice.
-* The API may change in incompatible ways in a later software release without notice.
-* Recommended for use only in short-lived testing clusters, due to increased
-  risk of bugs and lack of long-term support.
-
-A *Beta* feature means:
-
-* Enabled by default.
-* The feature is well tested. Enabling the feature is considered safe.
-* Support for the overall feature will not be dropped, though details may change.
-* The schema and/or semantics of objects may change in incompatible ways in a
-  subsequent beta or stable release. When this happens, we will provide instructions
-  for migrating to the next version. This may require deleting, editing, and
-  re-creating API objects. The editing process may require some thought.
-  This may require downtime for applications that rely on the feature.
-* Recommended for only non-business-critical uses because of potential for
-  incompatible changes in subsequent releases. If you have multiple clusters
-  that can be upgraded independently, you may be able to relax this restriction.
-
-{{< note >}}
-Please do try *Beta* features and give feedback on them!
-After they exit beta, it may not be practical for us to make more changes.
-{{< /note >}}
-
-A *GA* feature is also referred to as a *stable* feature. It means:
-
-* The corresponding feature gate is no longer needed.
-* Stable versions of features will appear in released software for many subsequent versions.
-
-### Feature Gates
-
-Each feature gate is designed for enabling/disabling a specific feature:
-
-- `Accelerators`: Enable Nvidia GPU support when using Docker
-- `AdvancedAuditing`: Enable [advanced auditing](/docs/tasks/debug-application-cluster/audit/#advanced-audit)
-- `AffinityInAnnotations`(*deprecated*): Enable setting [Pod affinity or anti-affinitys](/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
-- `AllowExtTrafficLocalEndpoints`: Enable a service to route external requests to node local endpoints.
-- `APIListChunking`: Enable the API clients to retrieve (`LIST` or `GET`) resources from API server in chunks.
-- `APIResponseCompression`: Compress the API responses for `LIST` or `GET` requests.
-- `AppArmor`: Enable AppArmor based mandatory access control on Linux nodes when using Docker.
-   See [AppArmor Tutorial](/docs/tutorials/clusters/apparmor/) for more details.
-- `AttachVolumeLimit`: Enable volume plugins to report limits on number of volumes
-  that can be attached to a node.
-   See [dynamic volume limits](/docs/concepts/storage/storage-limits/#dynamic-volume-limits) for more details.
-- `BlockVolume`: Enable the definition and consumption of raw block devices in Pods.
-   See [Raw Block Volume Support](/docs/concepts/storage/persistent-volumes/#raw-block-volume-support)
-   for more details.
-- `BoundServiceAccountTokenVolume`: Migrate ServiceAccount volumes to use a projected volume consisting of a
-   ServiceAccountTokenVolumeProjection.
-   Check [Service Account Token Volumes](https://git.k8s.io/community/contributors/design-proposals/storage/svcacct-token-volume-source.md)
-   for more details.
-- `CPUManager`: Enable container level CPU affinity support, see [CPU Management Policies](/docs/tasks/administer-cluster/cpu-management-policies/).
-- `CRIContainerLogRotation`: Enable container log rotation for cri container runtime.
-- `CSIBlockVolume`: Enable external CSI volume drivers to support block storage. See the [`csi` raw block volume support](/docs/concepts/storage/volumes/#csi-raw-block-volume-support) documentation for more details.
-- `CSIDriverRegistry`: Enable all logic related to the CSIDriver API object in csi.storage.k8s.io.
-- `CSIMigration`: Enables shims and translation logic to route volume operations from in-tree plugins to corresponding pre-installed CSI plugins
-- `CSIMigrationAWS`: Enables shims and translation logic to route volume operations from the AWS-EBS in-tree plugin to EBS CSI plugin
-- `CSIMigrationAzureDisk`: Enables shims and translation logic to route volume operations from the Azure-Disk in-tree plugin to Azure Disk CSI plugin
-- `CSIMigrationAzureFile`: Enables shims and translation logic to route volume operations from the Azure-File in-tree plugin to Azure File CSI plugin
-- `CSIMigrationGCE`: Enables shims and translation logic to route volume operations from the GCE-PD in-tree plugin to PD CSI plugin
-- `CSIMigrationOpenStack`: Enables shims and translation logic to route volume operations from the Cinder in-tree plugin to Cinder CSI plugin
-- `CSINodeInfo`: Enable all logic related to the CSINodeInfo API object in csi.storage.k8s.io.
-- `CSIPersistentVolume`: Enable discovering and mounting volumes provisioned through a
-  [CSI (Container Storage Interface)](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/storage/container-storage-interface.md)
-  compatible volume plugin.
-  Check the [`csi` volume type](/docs/concepts/storage/volumes/#csi) documentation for more details.
-- `CustomCPUCFSQuotaPeriod`: Enable nodes to change CPUCFSQuotaPeriod.
-- `CustomPodDNS`: Enable customizing the DNS settings for a Pod using its `dnsConfig` property.
-   Check [Pod's DNS Config](/docs/concepts/services-networking/dns-pod-service/#pods-dns-config)
-   for more details.
-- `CustomResourceSubresources`: Enable `/status` and `/scale` subresources
-  on resources created from [CustomResourceDefinition](/docs/concepts/api-extension/custom-resources/).
-- `CustomResourceValidation`: Enable schema based validation on resources created from
-  [CustomResourceDefinition](/docs/concepts/api-extension/custom-resources/).
-- `CustomResourceWebhookConversion`: Enable webhook-based conversion
-  on resources created from [CustomResourceDefinition](/docs/concepts/api-extension/custom-resources/).
-- `DebugContainers`: Enable running a "debugging" container in a Pod's namespace to
-  troubleshoot a running Pod.
-- `DevicePlugins`: Enable the [device-plugins](/docs/concepts/cluster-administration/device-plugins/)
-  based resource provisioning on nodes.
-- `DryRun`: Enable server-side [dry run](/docs/reference/using-api/api-concepts/#dry-run) requests.
-- `DynamicAuditing`: Enable [dynamic auditing](/docs/tasks/debug-application-cluster/audit/#dynamic-backend)
-- `DynamicKubeletConfig`: Enable the dynamic configuration of kubelet. See [Reconfigure kubelet](/docs/tasks/administer-cluster/reconfigure-kubelet/).
-- `DynamicProvisioningScheduling`: Extend the default scheduler to be aware of volume topology and handle PV provisioning.
-  This feature is superceded by the `VolumeScheduling` feature completely in v1.12.
-- `DynamicVolumeProvisioning`(*deprecated*): Enable the [dynamic provisioning](/docs/concepts/storage/dynamic-provisioning/) of persistent volumes to Pods.
-- `EnableEquivalenceClassCache`: Enable the scheduler to cache equivalence of nodes when scheduling Pods.
-- `ExpandInUsePersistentVolumes`: Enable expanding in-use PVCs. See [Resizing an in-use PersistentVolumeClaim](/docs/concepts/storage/persistent-volumes/#resizing-an-in-use-persistentvolumeclaim).
-- `ExpandPersistentVolumes`: Enable the expanding of persistent volumes. See [Expanding Persistent Volumes Claims](/docs/concepts/storage/persistent-volumes/#expanding-persistent-volumes-claims).
-- `ExperimentalCriticalPodAnnotation`: Enable annotating specific pods as *critical* so that their [scheduling is guaranteed](/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/).
-- `ExperimentalHostUserNamespaceDefaultingGate`: Enabling the defaulting user
-   namespace to host. This is for containers that are using other host namespaces,
-   host mounts, or containers that are privileged or using specific non-namespaced
-   capabilities (e.g. `MKNODE`, `SYS_MODULE` etc.). This should only be enabled
-   if user namespace remapping is enabled in the Docker daemon.
-- `GCERegionalPersistentDisk`: Enable the regional PD feature on GCE.
-- `HugePages`: Enable the allocation and consumption of pre-allocated [huge pages](/docs/tasks/manage-hugepages/scheduling-hugepages/).
-- `HyperVContainer`: Enable [Hyper-V isolation](https://docs.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/hyperv-container) for Windows containers.
-- `KubeletConfigFile`: Enable loading kubelet configuration from a file specified using a config file.
-  See [setting kubelet parameters via a config file](/docs/tasks/administer-cluster/kubelet-config-file/) for more details.
-- `KubeletPluginsWatcher`: Enable probe-based plugin watcher utility to enable kubelet
-  to discover plugins such as [CSI volume drivers](/docs/concepts/storage/volumes/#csi).
-- `KubeletPodResources`: Enable the kubelet's pod resources grpc endpoint.
-   See [Support Device Monitoring](https://git.k8s.io/community/keps/sig-node/compute-device-assignment.md) for more details.
-- `LocalStorageCapacityIsolation`: Enable the consumption of [local ephemeral storage](/docs/concepts/configuration/manage-compute-resources-container/) and also the `sizeLimit` property of an [emptyDir volume](/docs/concepts/storage/volumes/#emptydir).
-- `LocalStorageCapacityIsolationFSQuotaMonitoring`: When `LocalStorageCapacityIsolation` is enabled for [local ephemeral storage](/docs/concepts/configuration/manage-compute-resources-container/) and the backing filesystem for [emptyDir volumes](/docs/concepts/storage/volumes/#emptydir) supports project quotas and they are enabled, use project quotas to monitor [emptyDir volume](/docs/concepts/storage/volumes/#emptydir) storage consumption rather than filesystem walk for better performance and accuracy.
-- `MountContainers`: Enable using utility containers on host as the volume mounter.
-- `MountPropagation`: Enable sharing volume mounted by one container to other containers or pods.
-  For more details, please see [mount propagation](/docs/concepts/storage/volumes/#mount-propagation).
-- `NodeLease`: Enable the new Lease API to report node heartbeats, which could be used as a node health signal.
-- `PersistentLocalVolumes`: Enable the usage of `local` volume type in Pods.
-  Pod affinity has to be specified if requesting a `local` volume.
-- `PodPriority`: Enable the descheduling and preemption of Pods based on their [priorities](/docs/concepts/configuration/pod-priority-preemption/).
-- `PodReadinessGates`: Enable the setting of `PodReadinessGate` field for extending
-  Pod readiness evaluation.
-  For more details, please see [Pod readiness gate](/docs/concepts/workloads/pods/pod-lifecycle/#pod-readiness-gate).
-- `ProcMountType`: Enables control over ProcMountType for containers.
-- `PVCProtection`: Enable the prevention of a PersistentVolumeClaim (PVC) from
-  being deleted when it is still used by any Pod.
-  More details can be found [here](/docs/tasks/administer-cluster/storage-object-in-use-protection/).
-- `ResourceLimitsPriorityFunction`: Enable a scheduler priority function that
-  assigns a lowest possible score of 1 to a node that satisfies at least one of
-  the input Pod's cpu and memory limits. The intent is to break ties between
-  nodes with same scores.
-- `ResourceQuotaScopeSelectors`: Enable resource quota scope selectors.
-- `RotateKubeletClientCertificate`: Enable the rotation of the client TLS certificate on the kubelet.
-  See [kubelet configuration](/docs/reference/command-line-tools-reference/kubelet-tls-bootstrapping/#kubelet-configuration) for more details.
-- `RotateKubeletServerCertificate`: Enable the rotation of the server TLS certificate on the kubelet.
-  See [kubelet configuration](/docs/reference/command-line-tools-reference/kubelet-tls-bootstrapping/#kubelet-configuration) for more details.
-- `RunAsGroup`: Enable control over the primary group ID set on the init processes of containers.
-- `RuntimeClass`: Enable the [RuntimeClass](/docs/concepts/containers/runtime-class/) feature for selecting container runtime configurations.
-- `ScheduleDaemonSetPods`: Enable DaemonSet Pods to be scheduled by the default scheduler instead of the DaemonSet controller.
-- `SCTPSupport`: Enables the usage of SCTP as `protocol` value in `Service`, `Endpoint`, `NetworkPolicy` and `Pod` definitions
-- `ServerSideApply`: Enables the [Sever Side Apply (SSA)](/docs/reference/using-api/api-concepts/#server-side-apply) path at the API Server.
-- `ServiceNodeExclusion`: Enable the exclusion of nodes from load balancers created by a cloud provider.
-  A node is eligible for exclusion if annotated with "`alpha.service-controller.kubernetes.io/exclude-balancer`" key.
-- `StorageObjectInUseProtection`: Postpone the deletion of PersistentVolume or
-  PersistentVolumeClaim objects if they are still being used.
-- `StreamingProxyRedirects`: Instructs the API server to intercept (and follow)
-   redirects from the backend (kubelet) for streaming requests.
-  Examples of streaming requests include the `exec`, `attach` and `port-forward` requests.
-- `SupportIPVSProxyMode`: Enable providing in-cluster service load balancing using IPVS.
-  See [service proxies](/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies) for more details.
-- `SupportPodPidsLimit`: Enable the support to limiting PIDs in Pods.
-- `Sysctls`: Enable support for namespaced kernel parameters (sysctls) that can be set for each pod.
-  See [sysctls](/docs/tasks/administer-cluster/sysctl-cluster/) for more details.
-- `TaintBasedEvictions`: Enable evicting pods from nodes based on taints on nodes and tolerations on Pods.
-  See [taints and tolerations](/docs/concepts/configuration/taint-and-toleration/) for more details.
-- `TaintNodesByCondition`: Enable automatic tainting nodes based on [node conditions](/docs/concepts/architecture/nodes/#condition).
-- `TokenRequest`: Enable the `TokenRequest` endpoint on service account resources.
-- `TokenRequestProjection`: Enable the injection of service account tokens into
-  a Pod through the [`projected` volume](/docs/concepts/storage/volumes/#projected).
-- `TTLAfterFinished`: Allow a [TTL controller](/docs/concepts/workloads/controllers/ttlafterfinished/) to clean up resources after they finish execution.
-- `VolumeScheduling`: Enable volume topology aware scheduling and make the
-  PersistentVolumeClaim (PVC) binding aware of scheduling decisions. It also
-  enables the usage of [`local`](/docs/concepts/storage/volumes/#local) volume
-  type when used together with the `PersistentLocalVolumes` feature gate.
-- `VolumeSnapshotDataSource`: Enable volume snapshot data source support.
-- `VolumeSubpathEnvExpansion`: Enable `subPathExpr` field for expanding environment variables into a `subPath`.
-- `WindowsGMSA`: Enables passing of GMSA credential specs from pods to container runtimes.
-
-{{% /capture %}}

content/en/docs/reference/command-line-tools-reference/federation-apiserver_BACKUP_76806.md

@@ -1,154 +0,0 @@
----
-title: federation-apiserver
-notitle: true
----
-
-## federation-apiserver
-
-
-
-### Synopsis
-
-
-The Kubernetes federation API server validates and configures data
-for the api objects which include pods, services, replicationcontrollers, and
-others. The API Server services REST operations and provides the frontend to the
-cluster's shared state through which all other components interact.
-
-```
-federation-apiserver [flags]
-```
-
-### Options
-
-```
-      --admission-control-config-file string                    File with admission control configuration.
-      --advertise-address ip                                    The IP address on which to advertise the apiserver to members of the cluster. This address must be reachable by the rest of the cluster. If blank, the --bind-address will be used. If --bind-address is unspecified, the host's default interface will be used.
-      --anonymous-auth                                          Enables anonymous requests to the secure port of the API server. Requests that are not rejected by another authentication method are treated as anonymous requests. Anonymous requests have a username of system:anonymous, and a group name of system:unauthenticated. (default true)
-      --audit-log-format string                                 Format of saved audits. "legacy" indicates 1-line text format for each event. "json" indicates structured json format. Requires the 'AdvancedAuditing' feature gate. Known formats are legacy,json. (default "json")
-      --audit-log-maxage int                                    The maximum number of days to retain old audit log files based on the timestamp encoded in their filename.
-      --audit-log-maxbackup int                                 The maximum number of old audit log files to retain.
-      --audit-log-maxsize int                                   The maximum size in megabytes of the audit log file before it gets rotated.
-      --audit-log-path string                                   If set, all requests coming to the apiserver will be logged to this file.  '-' means standard out.
-      --audit-policy-file string                                Path to the file that defines the audit policy configuration. Requires the 'AdvancedAuditing' feature gate. With AdvancedAuditing, a profile is required to enable auditing.
-      --audit-webhook-batch-buffer-size int                     The size of the buffer to store events before batching and sending to the webhook. Only used in batch mode. (default 10000)
-      --audit-webhook-batch-initial-backoff duration            The amount of time to wait before retrying the first failed requests. Only used in batch mode. (default 10s)
-      --audit-webhook-batch-max-size int                        The maximum size of a batch sent to the webhook. Only used in batch mode. (default 400)
-      --audit-webhook-batch-max-wait duration                   The amount of time to wait before force sending the batch that hadn't reached the max size. Only used in batch mode. (default 30s)
-      --audit-webhook-batch-throttle-burst int                  Maximum number of requests sent at the same moment if ThrottleQPS was not utilized before. Only used in batch mode. (default 15)
-      --audit-webhook-batch-throttle-qps float32                Maximum average number of requests per second. Only used in batch mode. (default 10)
-      --audit-webhook-config-file string                        Path to a kubeconfig formatted file that defines the audit webhook configuration. Requires the 'AdvancedAuditing' feature gate.
-      --audit-webhook-mode string                               Strategy for sending audit events. Blocking indicates sending events should block server responses. Batch causes the webhook to buffer and send events asynchronously. Known modes are batch,blocking. (default "batch")
-      --authentication-token-webhook-cache-ttl duration         The duration to cache responses from the webhook token authenticator. (default 2m0s)
-      --authentication-token-webhook-config-file string         File with webhook configuration for token authentication in kubeconfig format. The API server will query the remote service to determine authentication for bearer tokens.
-      --authorization-mode string                               Ordered list of plug-ins to do authorization on secure port. Comma-delimited list of: AlwaysAllow,AlwaysDeny,ABAC,Webhook,RBAC,Node. (default "AlwaysAllow")
-      --authorization-policy-file string                        File with authorization policy in csv format, used with --authorization-mode=ABAC, on the secure port.
-      --authorization-webhook-cache-authorized-ttl duration     The duration to cache 'authorized' responses from the webhook authorizer. (default 5m0s)
-      --authorization-webhook-cache-unauthorized-ttl duration   The duration to cache 'unauthorized' responses from the webhook authorizer. (default 30s)
-      --authorization-webhook-config-file string                File with webhook configuration in kubeconfig format, used with --authorization-mode=Webhook. The API server will query the remote service to determine access on the API server's secure port.
-      --basic-auth-file string                                  If set, the file that will be used to admit requests to the secure port of the API server via http basic authentication.
-      --bind-address ip                                         The IP address on which to listen for the --secure-port port. The associated interface(s) must be reachable by the rest of the cluster, and by CLI/web clients. If blank, all interfaces will be used (0.0.0.0). (default 0.0.0.0)
-      --cert-dir string                                         The directory where the TLS certs are located. If --tls-cert-file and --tls-private-key-file are provided, this flag will be ignored. (default "/var/run/kubernetes")
-      --client-ca-file string                                   If set, any request presenting a client certificate signed by one of the authorities in the client-ca-file is authenticated with an identity corresponding to the CommonName of the client certificate.
-      --contention-profiling                                    Enable lock contention profiling, if profiling is enabled
-      --cors-allowed-origins strings                            List of allowed origins for CORS, comma separated.  An allowed origin can be a regular expression to support subdomain matching. If this list is empty CORS will not be enabled.
-      --default-watch-cache-size int                            Default watch cache size. If zero, watch cache will be disabled for resources that do not have a default watch size set. (default 100)
-      --delete-collection-workers int                           Number of workers spawned for DeleteCollection call. These are used to speed up namespace cleanup. (default 1)
-      --deserialization-cache-size int                          Number of deserialized json objects to cache in memory.
-      --disable-admission-plugins strings                       admission plugins that should be disabled although they are in the default enabled plugins list. Comma-delimited list of admission plugins: Initializers, MutatingAdmissionWebhook, NamespaceLifecycle, ValidatingAdmissionWebhook. The order of plugins in this flag does not matter.
-      --enable-admission-plugins strings                        admission plugins that should be enabled in addition to default enabled ones. Comma-delimited list of admission plugins: Initializers, MutatingAdmissionWebhook, NamespaceLifecycle, ValidatingAdmissionWebhook. The order of plugins in this flag does not matter.
-      --enable-bootstrap-token-auth                             Enable to allow secrets of type 'bootstrap.kubernetes.io/token' in the 'kube-system' namespace to be used for TLS bootstrapping authentication.
-      --enable-garbage-collector                                Enables the generic garbage collector. MUST be synced with the corresponding flag of the kube-controller-manager. (default true)
-      --enable-swagger-ui                                       Enables swagger ui on the apiserver at /swagger-ui
-      --etcd-cafile string                                      SSL Certificate Authority file used to secure etcd communication.
-      --etcd-certfile string                                    SSL certification file used to secure etcd communication.
-      --etcd-compaction-interval duration                       The interval of compaction requests. If 0, the compaction request from apiserver is disabled. (default 5m0s)
-      --etcd-keyfile string                                     SSL key file used to secure etcd communication.
-      --etcd-prefix string                                      The prefix to prepend to all resource paths in etcd. (default "/registry")
-      --etcd-servers strings                                    List of etcd servers to connect with (scheme://ip:port), comma separated.
-      --etcd-servers-overrides strings                          Per-resource etcd servers overrides, comma separated. The individual override format: group/resource#servers, where servers are http://ip:port, semicolon separated.
-      --event-ttl duration                                      Amount of time to retain events. (default 1h0m0s)
-      --encryption-provider-config string                       The file containing configuration for encryption providers to be used for storing secrets in etcd
-      --experimental-keystone-ca-file string                    If set, the Keystone server's certificate will be verified by one of the authorities in the experimental-keystone-ca-file, otherwise the host's root CA set will be used.
-      --experimental-keystone-url string                        If passed, activates the keystone authentication plugin.
-      --external-hostname string                                The hostname to use when generating externalized URLs for this master (e.g. Swagger API Docs).
-      --feature-gates mapStringBool                             A set of key=value pairs that describe feature gates for alpha/experimental features. Options are:
-APIListChunking=true|false (BETA - default=true)
-APIResponseCompression=true|false (ALPHA - default=false)
-Accelerators=true|false (ALPHA - default=false)
-AdvancedAuditing=true|false (BETA - default=true)
-AllAlpha=true|false (ALPHA - default=false)
-AppArmor=true|false (BETA - default=true)
-BlockVolume=true|false (ALPHA - default=false)
-CPUManager=true|false (BETA - default=true)
-CSIPersistentVolume=true|false (ALPHA - default=false)
-CustomPodDNS=true|false (ALPHA - default=false)
-CustomResourceValidation=true|false (BETA - default=true)
-DebugContainers=true|false (ALPHA - default=false)
-DevicePlugins=true|false (ALPHA - default=false)
-DynamicKubeletConfig=true|false (ALPHA - default=false)
-EnableEquivalenceClassCache=true|false (ALPHA - default=false)
-ExpandPersistentVolumes=true|false (ALPHA - default=false)
-ExperimentalCriticalPodAnnotation=true|false (ALPHA - default=false)
-ExperimentalHostUserNamespaceDefaulting=true|false (BETA - default=false)
-HugePages=true|false (BETA - default=true)
-HyperVContainer=true|false (ALPHA - default=false)
-Initializers=true|false (ALPHA - default=false)
-LocalStorageCapacityIsolation=true|false (ALPHA - default=false)
-LocalStorageCapacityIsolationFSQuotaMonitoring=true|false (ALPHA - default=false)
-MountContainers=true|false (ALPHA - default=false)
-MountPropagation=true|false (ALPHA - default=false)
-PVCProtection=true|false (ALPHA - default=false)
-PersistentLocalVolumes=true|false (ALPHA - default=false)
-PodPriority=true|false (ALPHA - default=false)
-PodShareProcessNamespace=true|false (ALPHA - default=false)
-ResourceLimitsPriorityFunction=true|false (ALPHA - default=false)
-RotateKubeletClientCertificate=true|false (BETA - default=true)
-RotateKubeletServerCertificate=true|false (ALPHA - default=false)
-ServiceNodeExclusion=true|false (ALPHA - default=false)
-ServiceProxyAllowExternalIPs=true|false (DEPRECATED - default=false)
-StreamingProxyRedirects=true|false (BETA - default=true)
-SupportIPVSProxyMode=true|false (BETA - default=false)
-SupportPodPidsLimit=true|false (ALPHA - default=false)
-TaintBasedEvictions=true|false (ALPHA - default=false)
-TaintNodesByCondition=true|false (ALPHA - default=false)
-VolumeScheduling=true|false (ALPHA - default=false)
-  -h, --help                                                    help for federation-apiserver
-      --log-flush-frequency duration                            Maximum number of seconds between log flushes (default 5s)
-      --master-service-namespace string                         DEPRECATED: the namespace from which the kubernetes master services should be injected into pods. (default "default")
-      --max-mutating-requests-inflight int                      The maximum number of mutating requests in flight at a given time. When the server exceeds this, it rejects requests. Zero for no limit. (default 200)
-      --max-requests-inflight int                               The maximum number of non-mutating requests in flight at a given time. When the server exceeds this, it rejects requests. Zero for no limit. (default 400)
-      --min-request-timeout int                                 An optional field indicating the minimum number of seconds a handler must keep a request open before timing it out. Currently only honored by the watch request handler, which picks a randomized value above this number as the connection timeout, to spread out load. (default 1800)
-      --oidc-ca-file string                                     If set, the OpenID server's certificate will be verified by one of the authorities in the oidc-ca-file, otherwise the host's root CA set will be used.
-      --oidc-client-id string                                   The client ID for the OpenID Connect client, must be set if oidc-issuer-url is set.
-      --oidc-groups-claim string                                If provided, the name of a custom OpenID Connect claim for specifying user groups. The claim value is expected to be a string or array of strings. This flag is experimental, please see the authentication documentation for further details.
-      --oidc-groups-prefix string                               If provided, all groups will be prefixed with this value to prevent conflicts with other authentication strategies.
-      --oidc-issuer-url string                                  The URL of the OpenID issuer, only HTTPS scheme will be accepted. If set, it will be used to verify the OIDC JSON Web Token (JWT).
-      --oidc-username-claim string                              The OpenID claim to use as the user name. Note that claims other than the default ('sub') is not guaranteed to be unique and immutable. This flag is experimental, please see the authentication documentation for further details. (default "sub")
-      --oidc-username-prefix string                             If provided, all usernames will be prefixed with this value. If not provided, username claims other than 'email' are prefixed by the issuer URL to avoid clashes. To skip any prefixing, provide the value '-'.
-      --profiling                                               Enable profiling via web interface host:port/debug/pprof/ (default true)
-      --request-timeout duration                                An optional field indicating the duration a handler must keep a request open before timing it out. This is the default request timeout for requests but may be overridden by flags such as --min-request-timeout for specific types of requests. (default 1m0s)
-      --requestheader-allowed-names strings                     List of client certificate common names to allow to provide usernames in headers specified by --requestheader-username-headers. If empty, any client certificate validated by the authorities in --requestheader-client-ca-file is allowed.
-      --requestheader-client-ca-file string                     Root certificate bundle to use to verify client certificates on incoming requests before trusting usernames in headers specified by --requestheader-username-headers
-      --requestheader-extra-headers-prefix strings              List of request header prefixes to inspect. X-Remote-Extra- is suggested.
-      --requestheader-group-headers strings                     List of request headers to inspect for groups. X-Remote-Group is suggested.
-      --requestheader-username-headers strings                  List of request headers to inspect for usernames. X-Remote-User is common.
-      --runtime-config mapStringString                          A set of key=value pairs that describe runtime configuration that may be passed to apiserver. <group>/<version> (or <version> for the core group) key can be used to turn on/off specific api versions. api/all is special key to control all api versions, be careful setting it false, unless you know what you do. api/legacy is deprecated, we will remove it in the future, so stop using it.
-      --secure-port int                                         The port on which to serve HTTPS with authentication and authorization. If 0, don't serve HTTPS at all. (default 6443)
-      --service-account-key-file stringArray                    File containing PEM-encoded x509 RSA or ECDSA private or public keys, used to verify ServiceAccount tokens. If unspecified, --tls-private-key-file is used. The specified file can contain multiple keys, and the flag can be specified multiple times with different files.
-      --service-account-lookup                                  If true, validate ServiceAccount tokens exist in etcd as part of authentication. (default true)
-      --storage-backend string                                  The storage backend for persistence. Options: 'etcd3' (default), 'etcd2'.
-      --storage-media-type string                               The media type to use to store objects in storage. Some resources or storage backends may only support a specific media type and will ignore this setting. (default "application/vnd.kubernetes.protobuf")
-      --storage-versions string                                 The per-group version to store resources in. Specified in the format "group1/version1,group2/version2,...". In the case where objects are moved from one group to the other, you may specify the format "group1=group2/v1beta1,group3/v1beta1,...". You only need to pass the groups you wish to change from the defaults. It defaults to a list of preferred versions of all registered groups, which is derived from the KUBE_API_VERSIONS environment variable. (default "admissionregistration.k8s.io/v1beta1,apps/v1beta1,authentication.k8s.io/v1,authorization.k8s.io/v1,autoscaling/v1,batch/v1,certificates.k8s.io/v1beta1,componentconfig/v1alpha1,events.k8s.io/v1beta1,extensions/v1beta1,federation/v1beta1,imagepolicy.k8s.io/v1alpha1,networking.k8s.io/v1,policy/v1beta1,rbac.authorization.k8s.io/v1,scheduling.k8s.io/v1alpha1,settings.k8s.io/v1alpha1,storage.k8s.io/v1,v1")
-      --target-ram-mb int                                       Memory limit for apiserver in MB (used to configure sizes of caches, etc.)
-      --tls-cert-file string                                    File containing the default x509 Certificate for HTTPS. (CA cert, if any, concatenated after server cert). If HTTPS serving is enabled, and --tls-cert-file and --tls-private-key-file are not provided, a self-signed certificate and key are generated for the public address and saved to the directory specified by --cert-dir.
-      --tls-cipher-suites strings                               Comma-separated list of cipher suites for the server. Values are from tls package constants (https://golang.org/pkg/crypto/tls/#pkg-constants). If omitted, the default Go cipher suites will be used
-      --tls-min-version string                                  Minimum TLS version supported. Value must match version names from https://golang.org/pkg/crypto/tls/#pkg-constants.
-      --tls-private-key-file string                             File containing the default x509 private key matching --tls-cert-file.
-      --tls-sni-cert-key namedCertKey                           A pair of x509 certificate and private key file paths, optionally suffixed with a list of domain patterns which are fully qualified domain names, possibly with prefixed wildcard segments. If no domain patterns are provided, the names of the certificate are extracted. Non-wildcard matches trump over wildcard matches, explicit domain patterns trump over extracted names. For multiple key/certificate pairs, use the --tls-sni-cert-key multiple times. Examples: "example.crt,example.key" or "foo.crt,foo.key:*.foo.com,foo.com". (default [])
-      --token-auth-file string                                  If set, the file that will be used to secure the secure port of the API server via token authentication.
-      --watch-cache                                             Enable watch caching in the apiserver (default true)
-      --watch-cache-sizes strings                               List of watch cache sizes for every resource (pods, nodes, etc.), comma separated. The individual override format: resource[.group]#size, where resource is lowercase plural (no version), group is optional, and size is a number. It takes effect when watch-cache is enabled. Some resources (replicationcontrollers, endpoints, nodes, pods, services, apiservices.apiregistration.k8s.io) have system defaults set by heuristics, others default to default-watch-cache-size
-```
-
-###### Auto generated by spf13/cobra on 1-Dec-2018

content/en/docs/reference/command-line-tools-reference/federation-apiserver_BASE_76806.md

@@ -1,153 +0,0 @@
----
-title: federation-apiserver
-notitle: true
----
-
-## federation-apiserver
-
-
-
-### Synopsis
-
-
-The Kubernetes federation API server validates and configures data
-for the api objects which include pods, services, replicationcontrollers, and
-others. The API Server services REST operations and provides the frontend to the
-cluster's shared state through which all other components interact.
-
-```
-federation-apiserver [flags]
-```
-
-### Options
-
-```
-      --admission-control-config-file string                    File with admission control configuration.
-      --advertise-address ip                                    The IP address on which to advertise the apiserver to members of the cluster. This address must be reachable by the rest of the cluster. If blank, the --bind-address will be used. If --bind-address is unspecified, the host's default interface will be used.
-      --anonymous-auth                                          Enables anonymous requests to the secure port of the API server. Requests that are not rejected by another authentication method are treated as anonymous requests. Anonymous requests have a username of system:anonymous, and a group name of system:unauthenticated. (default true)
-      --audit-log-format string                                 Format of saved audits. "legacy" indicates 1-line text format for each event. "json" indicates structured json format. Requires the 'AdvancedAuditing' feature gate. Known formats are legacy,json. (default "json")
-      --audit-log-maxage int                                    The maximum number of days to retain old audit log files based on the timestamp encoded in their filename.
-      --audit-log-maxbackup int                                 The maximum number of old audit log files to retain.
-      --audit-log-maxsize int                                   The maximum size in megabytes of the audit log file before it gets rotated.
-      --audit-log-path string                                   If set, all requests coming to the apiserver will be logged to this file.  '-' means standard out.
-      --audit-policy-file string                                Path to the file that defines the audit policy configuration. Requires the 'AdvancedAuditing' feature gate. With AdvancedAuditing, a profile is required to enable auditing.
-      --audit-webhook-batch-buffer-size int                     The size of the buffer to store events before batching and sending to the webhook. Only used in batch mode. (default 10000)
-      --audit-webhook-batch-initial-backoff duration            The amount of time to wait before retrying the first failed requests. Only used in batch mode. (default 10s)
-      --audit-webhook-batch-max-size int                        The maximum size of a batch sent to the webhook. Only used in batch mode. (default 400)
-      --audit-webhook-batch-max-wait duration                   The amount of time to wait before force sending the batch that hadn't reached the max size. Only used in batch mode. (default 30s)
-      --audit-webhook-batch-throttle-burst int                  Maximum number of requests sent at the same moment if ThrottleQPS was not utilized before. Only used in batch mode. (default 15)
-      --audit-webhook-batch-throttle-qps float32                Maximum average number of requests per second. Only used in batch mode. (default 10)
-      --audit-webhook-config-file string                        Path to a kubeconfig formatted file that defines the audit webhook configuration. Requires the 'AdvancedAuditing' feature gate.
-      --audit-webhook-mode string                               Strategy for sending audit events. Blocking indicates sending events should block server responses. Batch causes the webhook to buffer and send events asynchronously. Known modes are batch,blocking. (default "batch")
-      --authentication-token-webhook-cache-ttl duration         The duration to cache responses from the webhook token authenticator. (default 2m0s)
-      --authentication-token-webhook-config-file string         File with webhook configuration for token authentication in kubeconfig format. The API server will query the remote service to determine authentication for bearer tokens.
-      --authorization-mode string                               Ordered list of plug-ins to do authorization on secure port. Comma-delimited list of: AlwaysAllow,AlwaysDeny,ABAC,Webhook,RBAC,Node. (default "AlwaysAllow")
-      --authorization-policy-file string                        File with authorization policy in csv format, used with --authorization-mode=ABAC, on the secure port.
-      --authorization-webhook-cache-authorized-ttl duration     The duration to cache 'authorized' responses from the webhook authorizer. (default 5m0s)
-      --authorization-webhook-cache-unauthorized-ttl duration   The duration to cache 'unauthorized' responses from the webhook authorizer. (default 30s)
-      --authorization-webhook-config-file string                File with webhook configuration in kubeconfig format, used with --authorization-mode=Webhook. The API server will query the remote service to determine access on the API server's secure port.
-      --basic-auth-file string                                  If set, the file that will be used to admit requests to the secure port of the API server via http basic authentication.
-      --bind-address ip                                         The IP address on which to listen for the --secure-port port. The associated interface(s) must be reachable by the rest of the cluster, and by CLI/web clients. If blank, all interfaces will be used (0.0.0.0). (default 0.0.0.0)
-      --cert-dir string                                         The directory where the TLS certs are located. If --tls-cert-file and --tls-private-key-file are provided, this flag will be ignored. (default "/var/run/kubernetes")
-      --client-ca-file string                                   If set, any request presenting a client certificate signed by one of the authorities in the client-ca-file is authenticated with an identity corresponding to the CommonName of the client certificate.
-      --contention-profiling                                    Enable lock contention profiling, if profiling is enabled
-      --cors-allowed-origins strings                            List of allowed origins for CORS, comma separated.  An allowed origin can be a regular expression to support subdomain matching. If this list is empty CORS will not be enabled.
-      --default-watch-cache-size int                            Default watch cache size. If zero, watch cache will be disabled for resources that do not have a default watch size set. (default 100)
-      --delete-collection-workers int                           Number of workers spawned for DeleteCollection call. These are used to speed up namespace cleanup. (default 1)
-      --deserialization-cache-size int                          Number of deserialized json objects to cache in memory.
-      --disable-admission-plugins strings                       admission plugins that should be disabled although they are in the default enabled plugins list. Comma-delimited list of admission plugins: Initializers, MutatingAdmissionWebhook, NamespaceLifecycle, ValidatingAdmissionWebhook. The order of plugins in this flag does not matter.
-      --enable-admission-plugins strings                        admission plugins that should be enabled in addition to default enabled ones. Comma-delimited list of admission plugins: Initializers, MutatingAdmissionWebhook, NamespaceLifecycle, ValidatingAdmissionWebhook. The order of plugins in this flag does not matter.
-      --enable-bootstrap-token-auth                             Enable to allow secrets of type 'bootstrap.kubernetes.io/token' in the 'kube-system' namespace to be used for TLS bootstrapping authentication.
-      --enable-garbage-collector                                Enables the generic garbage collector. MUST be synced with the corresponding flag of the kube-controller-manager. (default true)
-      --enable-swagger-ui                                       Enables swagger ui on the apiserver at /swagger-ui
-      --etcd-cafile string                                      SSL Certificate Authority file used to secure etcd communication.
-      --etcd-certfile string                                    SSL certification file used to secure etcd communication.
-      --etcd-compaction-interval duration                       The interval of compaction requests. If 0, the compaction request from apiserver is disabled. (default 5m0s)
-      --etcd-keyfile string                                     SSL key file used to secure etcd communication.
-      --etcd-prefix string                                      The prefix to prepend to all resource paths in etcd. (default "/registry")
-      --etcd-servers strings                                    List of etcd servers to connect with (scheme://ip:port), comma separated.
-      --etcd-servers-overrides strings                          Per-resource etcd servers overrides, comma separated. The individual override format: group/resource#servers, where servers are http://ip:port, semicolon separated.
-      --event-ttl duration                                      Amount of time to retain events. (default 1h0m0s)
-      --encryption-provider-config string                       The file containing configuration for encryption providers to be used for storing secrets in etcd
-      --experimental-keystone-ca-file string                    If set, the Keystone server's certificate will be verified by one of the authorities in the experimental-keystone-ca-file, otherwise the host's root CA set will be used.
-      --experimental-keystone-url string                        If passed, activates the keystone authentication plugin.
-      --external-hostname string                                The hostname to use when generating externalized URLs for this master (e.g. Swagger API Docs).
-      --feature-gates mapStringBool                             A set of key=value pairs that describe feature gates for alpha/experimental features. Options are:
-APIListChunking=true|false (BETA - default=true)
-APIResponseCompression=true|false (ALPHA - default=false)
-Accelerators=true|false (ALPHA - default=false)
-AdvancedAuditing=true|false (BETA - default=true)
-AllAlpha=true|false (ALPHA - default=false)
-AppArmor=true|false (BETA - default=true)
-BlockVolume=true|false (ALPHA - default=false)
-CPUManager=true|false (BETA - default=true)
-CSIPersistentVolume=true|false (ALPHA - default=false)
-CustomPodDNS=true|false (ALPHA - default=false)
-CustomResourceValidation=true|false (BETA - default=true)
-DebugContainers=true|false (ALPHA - default=false)
-DevicePlugins=true|false (ALPHA - default=false)
-DynamicKubeletConfig=true|false (ALPHA - default=false)
-EnableEquivalenceClassCache=true|false (ALPHA - default=false)
-ExpandPersistentVolumes=true|false (ALPHA - default=false)
-ExperimentalCriticalPodAnnotation=true|false (ALPHA - default=false)
-ExperimentalHostUserNamespaceDefaulting=true|false (BETA - default=false)
-HugePages=true|false (BETA - default=true)
-HyperVContainer=true|false (ALPHA - default=false)
-Initializers=true|false (ALPHA - default=false)
-LocalStorageCapacityIsolation=true|false (ALPHA - default=false)
-MountContainers=true|false (ALPHA - default=false)
-MountPropagation=true|false (ALPHA - default=false)
-PVCProtection=true|false (ALPHA - default=false)
-PersistentLocalVolumes=true|false (ALPHA - default=false)
-PodPriority=true|false (ALPHA - default=false)
-PodShareProcessNamespace=true|false (ALPHA - default=false)
-ResourceLimitsPriorityFunction=true|false (ALPHA - default=false)
-RotateKubeletClientCertificate=true|false (BETA - default=true)
-RotateKubeletServerCertificate=true|false (ALPHA - default=false)
-ServiceNodeExclusion=true|false (ALPHA - default=false)
-ServiceProxyAllowExternalIPs=true|false (DEPRECATED - default=false)
-StreamingProxyRedirects=true|false (BETA - default=true)
-SupportIPVSProxyMode=true|false (BETA - default=false)
-SupportPodPidsLimit=true|false (ALPHA - default=false)
-TaintBasedEvictions=true|false (ALPHA - default=false)
-TaintNodesByCondition=true|false (ALPHA - default=false)
-VolumeScheduling=true|false (ALPHA - default=false)
-  -h, --help                                                    help for federation-apiserver
-      --log-flush-frequency duration                            Maximum number of seconds between log flushes (default 5s)
-      --master-service-namespace string                         DEPRECATED: the namespace from which the kubernetes master services should be injected into pods. (default "default")
-      --max-mutating-requests-inflight int                      The maximum number of mutating requests in flight at a given time. When the server exceeds this, it rejects requests. Zero for no limit. (default 200)
-      --max-requests-inflight int                               The maximum number of non-mutating requests in flight at a given time. When the server exceeds this, it rejects requests. Zero for no limit. (default 400)
-      --min-request-timeout int                                 An optional field indicating the minimum number of seconds a handler must keep a request open before timing it out. Currently only honored by the watch request handler, which picks a randomized value above this number as the connection timeout, to spread out load. (default 1800)
-      --oidc-ca-file string                                     If set, the OpenID server's certificate will be verified by one of the authorities in the oidc-ca-file, otherwise the host's root CA set will be used.
-      --oidc-client-id string                                   The client ID for the OpenID Connect client, must be set if oidc-issuer-url is set.
-      --oidc-groups-claim string                                If provided, the name of a custom OpenID Connect claim for specifying user groups. The claim value is expected to be a string or array of strings. This flag is experimental, please see the authentication documentation for further details.
-      --oidc-groups-prefix string                               If provided, all groups will be prefixed with this value to prevent conflicts with other authentication strategies.
-      --oidc-issuer-url string                                  The URL of the OpenID issuer, only HTTPS scheme will be accepted. If set, it will be used to verify the OIDC JSON Web Token (JWT).
-      --oidc-username-claim string                              The OpenID claim to use as the user name. Note that claims other than the default ('sub') is not guaranteed to be unique and immutable. This flag is experimental, please see the authentication documentation for further details. (default "sub")
-      --oidc-username-prefix string                             If provided, all usernames will be prefixed with this value. If not provided, username claims other than 'email' are prefixed by the issuer URL to avoid clashes. To skip any prefixing, provide the value '-'.
-      --profiling                                               Enable profiling via web interface host:port/debug/pprof/ (default true)
-      --request-timeout duration                                An optional field indicating the duration a handler must keep a request open before timing it out. This is the default request timeout for requests but may be overridden by flags such as --min-request-timeout for specific types of requests. (default 1m0s)
-      --requestheader-allowed-names strings                     List of client certificate common names to allow to provide usernames in headers specified by --requestheader-username-headers. If empty, any client certificate validated by the authorities in --requestheader-client-ca-file is allowed.
-      --requestheader-client-ca-file string                     Root certificate bundle to use to verify client certificates on incoming requests before trusting usernames in headers specified by --requestheader-username-headers
-      --requestheader-extra-headers-prefix strings              List of request header prefixes to inspect. X-Remote-Extra- is suggested.
-      --requestheader-group-headers strings                     List of request headers to inspect for groups. X-Remote-Group is suggested.
-      --requestheader-username-headers strings                  List of request headers to inspect for usernames. X-Remote-User is common.
-      --runtime-config mapStringString                          A set of key=value pairs that describe runtime configuration that may be passed to apiserver. <group>/<version> (or <version> for the core group) key can be used to turn on/off specific api versions. api/all is special key to control all api versions, be careful setting it false, unless you know what you do. api/legacy is deprecated, we will remove it in the future, so stop using it.
-      --secure-port int                                         The port on which to serve HTTPS with authentication and authorization. If 0, don't serve HTTPS at all. (default 6443)
-      --service-account-key-file stringArray                    File containing PEM-encoded x509 RSA or ECDSA private or public keys, used to verify ServiceAccount tokens. If unspecified, --tls-private-key-file is used. The specified file can contain multiple keys, and the flag can be specified multiple times with different files.
-      --service-account-lookup                                  If true, validate ServiceAccount tokens exist in etcd as part of authentication. (default true)
-      --storage-backend string                                  The storage backend for persistence. Options: 'etcd3' (default), 'etcd2'.
-      --storage-media-type string                               The media type to use to store objects in storage. Some resources or storage backends may only support a specific media type and will ignore this setting. (default "application/vnd.kubernetes.protobuf")
-      --storage-versions string                                 The per-group version to store resources in. Specified in the format "group1/version1,group2/version2,...". In the case where objects are moved from one group to the other, you may specify the format "group1=group2/v1beta1,group3/v1beta1,...". You only need to pass the groups you wish to change from the defaults. It defaults to a list of preferred versions of all registered groups, which is derived from the KUBE_API_VERSIONS environment variable. (default "admissionregistration.k8s.io/v1beta1,apps/v1beta1,authentication.k8s.io/v1,authorization.k8s.io/v1,autoscaling/v1,batch/v1,certificates.k8s.io/v1beta1,componentconfig/v1alpha1,events.k8s.io/v1beta1,extensions/v1beta1,federation/v1beta1,imagepolicy.k8s.io/v1alpha1,networking.k8s.io/v1,policy/v1beta1,rbac.authorization.k8s.io/v1,scheduling.k8s.io/v1alpha1,settings.k8s.io/v1alpha1,storage.k8s.io/v1,v1")
-      --target-ram-mb int                                       Memory limit for apiserver in MB (used to configure sizes of caches, etc.)
-      --tls-cert-file string                                    File containing the default x509 Certificate for HTTPS. (CA cert, if any, concatenated after server cert). If HTTPS serving is enabled, and --tls-cert-file and --tls-private-key-file are not provided, a self-signed certificate and key are generated for the public address and saved to the directory specified by --cert-dir.
-      --tls-cipher-suites strings                               Comma-separated list of cipher suites for the server. Values are from tls package constants (https://golang.org/pkg/crypto/tls/#pkg-constants). If omitted, the default Go cipher suites will be used
-      --tls-min-version string                                  Minimum TLS version supported. Value must match version names from https://golang.org/pkg/crypto/tls/#pkg-constants.
-      --tls-private-key-file string                             File containing the default x509 private key matching --tls-cert-file.
-      --tls-sni-cert-key namedCertKey                           A pair of x509 certificate and private key file paths, optionally suffixed with a list of domain patterns which are fully qualified domain names, possibly with prefixed wildcard segments. If no domain patterns are provided, the names of the certificate are extracted. Non-wildcard matches trump over wildcard matches, explicit domain patterns trump over extracted names. For multiple key/certificate pairs, use the --tls-sni-cert-key multiple times. Examples: "example.crt,example.key" or "foo.crt,foo.key:*.foo.com,foo.com". (default [])
-      --token-auth-file string                                  If set, the file that will be used to secure the secure port of the API server via token authentication.
-      --watch-cache                                             Enable watch caching in the apiserver (default true)
-      --watch-cache-sizes strings                               List of watch cache sizes for every resource (pods, nodes, etc.), comma separated. The individual override format: resource[.group]#size, where resource is lowercase plural (no version), group is optional, and size is a number. It takes effect when watch-cache is enabled. Some resources (replicationcontrollers, endpoints, nodes, pods, services, apiservices.apiregistration.k8s.io) have system defaults set by heuristics, others default to default-watch-cache-size
-```
-
-###### Auto generated by spf13/cobra on 1-Dec-2018

content/en/docs/reference/command-line-tools-reference/federation-apiserver_LOCAL_76806.md

@@ -1,154 +0,0 @@
----
-title: federation-apiserver
-notitle: true
----
-
-## federation-apiserver
-
-
-
-### Synopsis
-
-
-The Kubernetes federation API server validates and configures data
-for the api objects which include pods, services, replicationcontrollers, and
-others. The API Server services REST operations and provides the frontend to the
-cluster's shared state through which all other components interact.
-
-```
-federation-apiserver [flags]
-```
-
-### Options
-
-```
-      --admission-control-config-file string                    File with admission control configuration.
-      --advertise-address ip                                    The IP address on which to advertise the apiserver to members of the cluster. This address must be reachable by the rest of the cluster. If blank, the --bind-address will be used. If --bind-address is unspecified, the host's default interface will be used.
-      --anonymous-auth                                          Enables anonymous requests to the secure port of the API server. Requests that are not rejected by another authentication method are treated as anonymous requests. Anonymous requests have a username of system:anonymous, and a group name of system:unauthenticated. (default true)
-      --audit-log-format string                                 Format of saved audits. "legacy" indicates 1-line text format for each event. "json" indicates structured json format. Requires the 'AdvancedAuditing' feature gate. Known formats are legacy,json. (default "json")
-      --audit-log-maxage int                                    The maximum number of days to retain old audit log files based on the timestamp encoded in their filename.
-      --audit-log-maxbackup int                                 The maximum number of old audit log files to retain.
-      --audit-log-maxsize int                                   The maximum size in megabytes of the audit log file before it gets rotated.
-      --audit-log-path string                                   If set, all requests coming to the apiserver will be logged to this file.  '-' means standard out.
-      --audit-policy-file string                                Path to the file that defines the audit policy configuration. Requires the 'AdvancedAuditing' feature gate. With AdvancedAuditing, a profile is required to enable auditing.
-      --audit-webhook-batch-buffer-size int                     The size of the buffer to store events before batching and sending to the webhook. Only used in batch mode. (default 10000)
-      --audit-webhook-batch-initial-backoff duration            The amount of time to wait before retrying the first failed requests. Only used in batch mode. (default 10s)
-      --audit-webhook-batch-max-size int                        The maximum size of a batch sent to the webhook. Only used in batch mode. (default 400)
-      --audit-webhook-batch-max-wait duration                   The amount of time to wait before force sending the batch that hadn't reached the max size. Only used in batch mode. (default 30s)
-      --audit-webhook-batch-throttle-burst int                  Maximum number of requests sent at the same moment if ThrottleQPS was not utilized before. Only used in batch mode. (default 15)
-      --audit-webhook-batch-throttle-qps float32                Maximum average number of requests per second. Only used in batch mode. (default 10)
-      --audit-webhook-config-file string                        Path to a kubeconfig formatted file that defines the audit webhook configuration. Requires the 'AdvancedAuditing' feature gate.
-      --audit-webhook-mode string                               Strategy for sending audit events. Blocking indicates sending events should block server responses. Batch causes the webhook to buffer and send events asynchronously. Known modes are batch,blocking. (default "batch")
-      --authentication-token-webhook-cache-ttl duration         The duration to cache responses from the webhook token authenticator. (default 2m0s)
-      --authentication-token-webhook-config-file string         File with webhook configuration for token authentication in kubeconfig format. The API server will query the remote service to determine authentication for bearer tokens.
-      --authorization-mode string                               Ordered list of plug-ins to do authorization on secure port. Comma-delimited list of: AlwaysAllow,AlwaysDeny,ABAC,Webhook,RBAC,Node. (default "AlwaysAllow")
-      --authorization-policy-file string                        File with authorization policy in csv format, used with --authorization-mode=ABAC, on the secure port.
-      --authorization-webhook-cache-authorized-ttl duration     The duration to cache 'authorized' responses from the webhook authorizer. (default 5m0s)
-      --authorization-webhook-cache-unauthorized-ttl duration   The duration to cache 'unauthorized' responses from the webhook authorizer. (default 30s)
-      --authorization-webhook-config-file string                File with webhook configuration in kubeconfig format, used with --authorization-mode=Webhook. The API server will query the remote service to determine access on the API server's secure port.
-      --basic-auth-file string                                  If set, the file that will be used to admit requests to the secure port of the API server via http basic authentication.
-      --bind-address ip                                         The IP address on which to listen for the --secure-port port. The associated interface(s) must be reachable by the rest of the cluster, and by CLI/web clients. If blank, all interfaces will be used (0.0.0.0). (default 0.0.0.0)
-      --cert-dir string                                         The directory where the TLS certs are located. If --tls-cert-file and --tls-private-key-file are provided, this flag will be ignored. (default "/var/run/kubernetes")
-      --client-ca-file string                                   If set, any request presenting a client certificate signed by one of the authorities in the client-ca-file is authenticated with an identity corresponding to the CommonName of the client certificate.
-      --contention-profiling                                    Enable lock contention profiling, if profiling is enabled
-      --cors-allowed-origins strings                            List of allowed origins for CORS, comma separated.  An allowed origin can be a regular expression to support subdomain matching. If this list is empty CORS will not be enabled.
-      --default-watch-cache-size int                            Default watch cache size. If zero, watch cache will be disabled for resources that do not have a default watch size set. (default 100)
-      --delete-collection-workers int                           Number of workers spawned for DeleteCollection call. These are used to speed up namespace cleanup. (default 1)
-      --deserialization-cache-size int                          Number of deserialized json objects to cache in memory.
-      --disable-admission-plugins strings                       admission plugins that should be disabled although they are in the default enabled plugins list. Comma-delimited list of admission plugins: Initializers, MutatingAdmissionWebhook, NamespaceLifecycle, ValidatingAdmissionWebhook. The order of plugins in this flag does not matter.
-      --enable-admission-plugins strings                        admission plugins that should be enabled in addition to default enabled ones. Comma-delimited list of admission plugins: Initializers, MutatingAdmissionWebhook, NamespaceLifecycle, ValidatingAdmissionWebhook. The order of plugins in this flag does not matter.
-      --enable-bootstrap-token-auth                             Enable to allow secrets of type 'bootstrap.kubernetes.io/token' in the 'kube-system' namespace to be used for TLS bootstrapping authentication.
-      --enable-garbage-collector                                Enables the generic garbage collector. MUST be synced with the corresponding flag of the kube-controller-manager. (default true)
-      --enable-swagger-ui                                       Enables swagger ui on the apiserver at /swagger-ui
-      --etcd-cafile string                                      SSL Certificate Authority file used to secure etcd communication.
-      --etcd-certfile string                                    SSL certification file used to secure etcd communication.
-      --etcd-compaction-interval duration                       The interval of compaction requests. If 0, the compaction request from apiserver is disabled. (default 5m0s)
-      --etcd-keyfile string                                     SSL key file used to secure etcd communication.
-      --etcd-prefix string                                      The prefix to prepend to all resource paths in etcd. (default "/registry")
-      --etcd-servers strings                                    List of etcd servers to connect with (scheme://ip:port), comma separated.
-      --etcd-servers-overrides strings                          Per-resource etcd servers overrides, comma separated. The individual override format: group/resource#servers, where servers are http://ip:port, semicolon separated.
-      --event-ttl duration                                      Amount of time to retain events. (default 1h0m0s)
-      --encryption-provider-config string                       The file containing configuration for encryption providers to be used for storing secrets in etcd
-      --experimental-keystone-ca-file string                    If set, the Keystone server's certificate will be verified by one of the authorities in the experimental-keystone-ca-file, otherwise the host's root CA set will be used.
-      --experimental-keystone-url string                        If passed, activates the keystone authentication plugin.
-      --external-hostname string                                The hostname to use when generating externalized URLs for this master (e.g. Swagger API Docs).
-      --feature-gates mapStringBool                             A set of key=value pairs that describe feature gates for alpha/experimental features. Options are:
-APIListChunking=true|false (BETA - default=true)
-APIResponseCompression=true|false (ALPHA - default=false)
-Accelerators=true|false (ALPHA - default=false)
-AdvancedAuditing=true|false (BETA - default=true)
-AllAlpha=true|false (ALPHA - default=false)
-AppArmor=true|false (BETA - default=true)
-BlockVolume=true|false (ALPHA - default=false)
-CPUManager=true|false (BETA - default=true)
-CSIPersistentVolume=true|false (ALPHA - default=false)
-CustomPodDNS=true|false (ALPHA - default=false)
-CustomResourceValidation=true|false (BETA - default=true)
-DebugContainers=true|false (ALPHA - default=false)
-DevicePlugins=true|false (ALPHA - default=false)
-DynamicKubeletConfig=true|false (ALPHA - default=false)
-EnableEquivalenceClassCache=true|false (ALPHA - default=false)
-ExpandPersistentVolumes=true|false (ALPHA - default=false)
-ExperimentalCriticalPodAnnotation=true|false (ALPHA - default=false)
-ExperimentalHostUserNamespaceDefaulting=true|false (BETA - default=false)
-HugePages=true|false (BETA - default=true)
-HyperVContainer=true|false (ALPHA - default=false)
-Initializers=true|false (ALPHA - default=false)
-LocalStorageCapacityIsolation=true|false (ALPHA - default=false)
-LocalStorageCapacityIsolationFSQuotaMonitoring=true|false (ALPHA - default=false)
-MountContainers=true|false (ALPHA - default=false)
-MountPropagation=true|false (ALPHA - default=false)
-PVCProtection=true|false (ALPHA - default=false)
-PersistentLocalVolumes=true|false (ALPHA - default=false)
-PodPriority=true|false (ALPHA - default=false)
-PodShareProcessNamespace=true|false (ALPHA - default=false)
-ResourceLimitsPriorityFunction=true|false (ALPHA - default=false)
-RotateKubeletClientCertificate=true|false (BETA - default=true)
-RotateKubeletServerCertificate=true|false (ALPHA - default=false)
-ServiceNodeExclusion=true|false (ALPHA - default=false)
-ServiceProxyAllowExternalIPs=true|false (DEPRECATED - default=false)
-StreamingProxyRedirects=true|false (BETA - default=true)
-SupportIPVSProxyMode=true|false (BETA - default=false)
-SupportPodPidsLimit=true|false (ALPHA - default=false)
-TaintBasedEvictions=true|false (ALPHA - default=false)
-TaintNodesByCondition=true|false (ALPHA - default=false)
-VolumeScheduling=true|false (ALPHA - default=false)
-  -h, --help                                                    help for federation-apiserver
-      --log-flush-frequency duration                            Maximum number of seconds between log flushes (default 5s)
-      --master-service-namespace string                         DEPRECATED: the namespace from which the kubernetes master services should be injected into pods. (default "default")
-      --max-mutating-requests-inflight int                      The maximum number of mutating requests in flight at a given time. When the server exceeds this, it rejects requests. Zero for no limit. (default 200)
-      --max-requests-inflight int                               The maximum number of non-mutating requests in flight at a given time. When the server exceeds this, it rejects requests. Zero for no limit. (default 400)
-      --min-request-timeout int                                 An optional field indicating the minimum number of seconds a handler must keep a request open before timing it out. Currently only honored by the watch request handler, which picks a randomized value above this number as the connection timeout, to spread out load. (default 1800)
-      --oidc-ca-file string                                     If set, the OpenID server's certificate will be verified by one of the authorities in the oidc-ca-file, otherwise the host's root CA set will be used.
-      --oidc-client-id string                                   The client ID for the OpenID Connect client, must be set if oidc-issuer-url is set.
-      --oidc-groups-claim string                                If provided, the name of a custom OpenID Connect claim for specifying user groups. The claim value is expected to be a string or array of strings. This flag is experimental, please see the authentication documentation for further details.
-      --oidc-groups-prefix string                               If provided, all groups will be prefixed with this value to prevent conflicts with other authentication strategies.
-      --oidc-issuer-url string                                  The URL of the OpenID issuer, only HTTPS scheme will be accepted. If set, it will be used to verify the OIDC JSON Web Token (JWT).
-      --oidc-username-claim string                              The OpenID claim to use as the user name. Note that claims other than the default ('sub') is not guaranteed to be unique and immutable. This flag is experimental, please see the authentication documentation for further details. (default "sub")
-      --oidc-username-prefix string                             If provided, all usernames will be prefixed with this value. If not provided, username claims other than 'email' are prefixed by the issuer URL to avoid clashes. To skip any prefixing, provide the value '-'.
-      --profiling                                               Enable profiling via web interface host:port/debug/pprof/ (default true)
-      --request-timeout duration                                An optional field indicating the duration a handler must keep a request open before timing it out. This is the default request timeout for requests but may be overridden by flags such as --min-request-timeout for specific types of requests. (default 1m0s)
-      --requestheader-allowed-names strings                     List of client certificate common names to allow to provide usernames in headers specified by --requestheader-username-headers. If empty, any client certificate validated by the authorities in --requestheader-client-ca-file is allowed.
-      --requestheader-client-ca-file string                     Root certificate bundle to use to verify client certificates on incoming requests before trusting usernames in headers specified by --requestheader-username-headers
-      --requestheader-extra-headers-prefix strings              List of request header prefixes to inspect. X-Remote-Extra- is suggested.
-      --requestheader-group-headers strings                     List of request headers to inspect for groups. X-Remote-Group is suggested.
-      --requestheader-username-headers strings                  List of request headers to inspect for usernames. X-Remote-User is common.
-      --runtime-config mapStringString                          A set of key=value pairs that describe runtime configuration that may be passed to apiserver. <group>/<version> (or <version> for the core group) key can be used to turn on/off specific api versions. api/all is special key to control all api versions, be careful setting it false, unless you know what you do. api/legacy is deprecated, we will remove it in the future, so stop using it.
-      --secure-port int                                         The port on which to serve HTTPS with authentication and authorization. If 0, don't serve HTTPS at all. (default 6443)
-      --service-account-key-file stringArray                    File containing PEM-encoded x509 RSA or ECDSA private or public keys, used to verify ServiceAccount tokens. If unspecified, --tls-private-key-file is used. The specified file can contain multiple keys, and the flag can be specified multiple times with different files.
-      --service-account-lookup                                  If true, validate ServiceAccount tokens exist in etcd as part of authentication. (default true)
-      --storage-backend string                                  The storage backend for persistence. Options: 'etcd3' (default), 'etcd2'.
-      --storage-media-type string                               The media type to use to store objects in storage. Some resources or storage backends may only support a specific media type and will ignore this setting. (default "application/vnd.kubernetes.protobuf")
-      --storage-versions string                                 The per-group version to store resources in. Specified in the format "group1/version1,group2/version2,...". In the case where objects are moved from one group to the other, you may specify the format "group1=group2/v1beta1,group3/v1beta1,...". You only need to pass the groups you wish to change from the defaults. It defaults to a list of preferred versions of all registered groups, which is derived from the KUBE_API_VERSIONS environment variable. (default "admissionregistration.k8s.io/v1beta1,apps/v1beta1,authentication.k8s.io/v1,authorization.k8s.io/v1,autoscaling/v1,batch/v1,certificates.k8s.io/v1beta1,componentconfig/v1alpha1,events.k8s.io/v1beta1,extensions/v1beta1,federation/v1beta1,imagepolicy.k8s.io/v1alpha1,networking.k8s.io/v1,policy/v1beta1,rbac.authorization.k8s.io/v1,scheduling.k8s.io/v1alpha1,settings.k8s.io/v1alpha1,storage.k8s.io/v1,v1")
-      --target-ram-mb int                                       Memory limit for apiserver in MB (used to configure sizes of caches, etc.)
-      --tls-cert-file string                                    File containing the default x509 Certificate for HTTPS. (CA cert, if any, concatenated after server cert). If HTTPS serving is enabled, and --tls-cert-file and --tls-private-key-file are not provided, a self-signed certificate and key are generated for the public address and saved to the directory specified by --cert-dir.
-      --tls-cipher-suites strings                               Comma-separated list of cipher suites for the server. Values are from tls package constants (https://golang.org/pkg/crypto/tls/#pkg-constants). If omitted, the default Go cipher suites will be used
-      --tls-min-version string                                  Minimum TLS version supported. Value must match version names from https://golang.org/pkg/crypto/tls/#pkg-constants.
-      --tls-private-key-file string                             File containing the default x509 private key matching --tls-cert-file.
-      --tls-sni-cert-key namedCertKey                           A pair of x509 certificate and private key file paths, optionally suffixed with a list of domain patterns which are fully qualified domain names, possibly with prefixed wildcard segments. If no domain patterns are provided, the names of the certificate are extracted. Non-wildcard matches trump over wildcard matches, explicit domain patterns trump over extracted names. For multiple key/certificate pairs, use the --tls-sni-cert-key multiple times. Examples: "example.crt,example.key" or "foo.crt,foo.key:*.foo.com,foo.com". (default [])
-      --token-auth-file string                                  If set, the file that will be used to secure the secure port of the API server via token authentication.
-      --watch-cache                                             Enable watch caching in the apiserver (default true)
-      --watch-cache-sizes strings                               List of watch cache sizes for every resource (pods, nodes, etc.), comma separated. The individual override format: resource[.group]#size, where resource is lowercase plural (no version), group is optional, and size is a number. It takes effect when watch-cache is enabled. Some resources (replicationcontrollers, endpoints, nodes, pods, services, apiservices.apiregistration.k8s.io) have system defaults set by heuristics, others default to default-watch-cache-size
-```
-
-###### Auto generated by spf13/cobra on 1-Dec-2018

content/en/docs/reference/command-line-tools-reference/kube-controller-manager.md.orig

@@ -1,808 +0,0 @@
----
-title: kube-controller-manager
-notitle: true
----
-## kube-controller-manager
-
-
-
-### Synopsis
-
-
-The Kubernetes controller manager is a daemon that embeds
-the core control loops shipped with Kubernetes. In applications of robotics and
-automation, a control loop is a non-terminating loop that regulates the state of
-the system. In Kubernetes, a controller is a control loop that watches the shared
-state of the cluster through the apiserver and makes changes attempting to move the
-current state towards the desired state. Examples of controllers that ship with
-Kubernetes today are the replication controller, endpoints controller, namespace
-controller, and serviceaccounts controller.
-
-```
-kube-controller-manager [flags]
-```
-
-### Options
-
-<table style="width: 100%; table-layout: fixed;">
-  <colgroup>
-    <col span="1" style="width: 10px;" />
-    <col span="1" />
-  </colgroup>
-  <tbody>
-
-    <tr>
-      <td colspan="2">--allocate-node-cidrs</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Should CIDRs for Pods be allocated and set on the cloud provider.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--alsologtostderr</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">log to standard error as well as files</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--attach-detach-reconcile-sync-period duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 1m0s</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The reconciler sync wait time between volume attach detach. This duration must be larger than one second, and increasing this value from the default may allow for volumes to be mismatched with pods.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--authentication-kubeconfig string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">kubeconfig file pointing at the 'core' kubernetes server with enough rights to create tokenaccessreviews.authentication.k8s.io. This is optional. If empty, all token requests are considered to be anonymous and no client CA is looked up in the cluster.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--authentication-skip-lookup</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">If false, the authentication-kubeconfig will be used to lookup missing authentication configuration from the cluster.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--authentication-token-webhook-cache-ttl duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 10s</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The duration to cache responses from the webhook token authenticator.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--authentication-tolerate-lookup-failure</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">If true, failures to look up missing authentication configuration from the cluster are not considered fatal. Note that this can result in authentication that treats all requests as anonymous.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--authorization-always-allow-paths stringSlice&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: [/healthz]</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">A list of HTTP paths to skip during authorization, i.e. these are authorized without contacting the 'core' kubernetes server.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--authorization-kubeconfig string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">kubeconfig file pointing at the 'core' kubernetes server with enough rights to create subjectaccessreviews.authorization.k8s.io. This is optional. If empty, all requests not skipped by authorization are forbidden.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--authorization-webhook-cache-authorized-ttl duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 10s</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The duration to cache 'authorized' responses from the webhook authorizer.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--authorization-webhook-cache-unauthorized-ttl duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 10s</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The duration to cache 'unauthorized' responses from the webhook authorizer.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--azure-container-registry-config string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Path to the file containing Azure container registry configuration information.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--bind-address ip&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 0.0.0.0</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The IP address on which to listen for the --secure-port port. The associated interface(s) must be reachable by the rest of the cluster, and by CLI/web clients. If blank, all interfaces will be used (0.0.0.0 for all IPv4 interfaces and :: for all IPv6 interfaces).</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--cert-dir string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The directory where the TLS certs are located. If --tls-cert-file and --tls-private-key-file are provided, this flag will be ignored.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--cidr-allocator-type string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "RangeAllocator"</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Type of CIDR allocator to use</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--client-ca-file string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">If set, any request presenting a client certificate signed by one of the authorities in the client-ca-file is authenticated with an identity corresponding to the CommonName of the client certificate.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--cloud-config string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The path to the cloud provider configuration file. Empty string for no configuration file.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--cloud-provider string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The provider for cloud services. Empty string for no provider.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--cluster-cidr string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">CIDR Range for Pods in cluster. Requires --allocate-node-cidrs to be true</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--cluster-name string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "kubernetes"</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The instance prefix for the cluster.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--cluster-signing-cert-file string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "/etc/kubernetes/ca/ca.pem"</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Filename containing a PEM-encoded X509 CA certificate used to issue cluster-scoped certificates</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--cluster-signing-key-file string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "/etc/kubernetes/ca/ca.key"</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Filename containing a PEM-encoded RSA or ECDSA private key used to sign cluster-scoped certificates</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--concurrent-deployment-syncs int32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 5</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The number of deployment objects that are allowed to sync concurrently. Larger number = more responsive deployments, but more CPU (and network) load</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--concurrent-endpoint-syncs int32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 5</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The number of endpoint syncing operations that will be done concurrently. Larger number = faster endpoint updating, but more CPU (and network) load</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--concurrent-gc-syncs int32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 20</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The number of garbage collector workers that are allowed to sync concurrently.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--concurrent-namespace-syncs int32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 10</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The number of namespace objects that are allowed to sync concurrently. Larger number = more responsive namespace termination, but more CPU (and network) load</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--concurrent-replicaset-syncs int32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 5</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The number of replica sets that are allowed to sync concurrently. Larger number = more responsive replica management, but more CPU (and network) load</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--concurrent-resource-quota-syncs int32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 5</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The number of resource quotas that are allowed to sync concurrently. Larger number = more responsive quota management, but more CPU (and network) load</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--concurrent-service-syncs int32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 1</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The number of services that are allowed to sync concurrently. Larger number = more responsive service management, but more CPU (and network) load</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--concurrent-serviceaccount-token-syncs int32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 5</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The number of service account token objects that are allowed to sync concurrently. Larger number = more responsive token generation, but more CPU (and network) load</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--concurrent-ttl-after-finished-syncs int32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 5</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The number of TTL-after-finished controller workers that are allowed to sync concurrently.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--concurrent_rc_syncs int32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 5</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The number of replication controllers that are allowed to sync concurrently. Larger number = more responsive replica management, but more CPU (and network) load</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--configure-cloud-routes&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: true</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Should CIDRs allocated by allocate-node-cidrs be configured on the cloud provider.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--contention-profiling</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Enable lock contention profiling, if profiling is enabled</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--controller-start-interval duration</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Interval between starting controller managers.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--controllers stringSlice&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: [*]</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">A list of controllers to enable. '*' enables all on-by-default controllers, 'foo' enables the controller named 'foo', '-foo' disables the controller named 'foo'.<br/>All controllers: attachdetach, bootstrapsigner, cloud-node-lifecycle, clusterrole-aggregation, cronjob, csrapproving, csrcleaner, csrsigning, daemonset, deployment, disruption, endpoint, garbagecollector, horizontalpodautoscaling, job, namespace, nodeipam, nodelifecycle, persistentvolume-binder, persistentvolume-expander, podgc, pv-protection, pvc-protection, replicaset, replicationcontroller, resourcequota, root-ca-cert-publisher, route, service, serviceaccount, serviceaccount-token, statefulset, tokencleaner, ttl, ttl-after-finished<br/>Disabled-by-default controllers: bootstrapsigner, tokencleaner</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--deployment-controller-sync-period duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 30s</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Period for syncing the deployments.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--disable-attach-detach-reconcile-sync</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Disable volume attach detach reconciler sync. Disabling this may cause volumes to be mismatched with pods. Use wisely.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--enable-dynamic-provisioning&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: true</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Enable dynamic provisioning for environments that support it.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--enable-garbage-collector&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: true</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Enables the generic garbage collector. MUST be synced with the corresponding flag of the kube-apiserver.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--enable-hostpath-provisioner</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Enable HostPath PV provisioning when running without a cloud provider. This allows testing and development of provisioning features.  HostPath provisioning is not supported in any way, won't work in a multi-node cluster, and should not be used for anything other than testing or development.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--enable-taint-manager&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: true</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">WARNING: Beta feature. If set to true enables NoExecute Taints and will evict all not-tolerating Pod running on Nodes tainted with this kind of Taints.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--experimental-cluster-signing-duration duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 8760h0m0s</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The length of duration signed certificates will be given.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--external-cloud-volume-plugin string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The plugin to use when cloud provider is set to external. Can be empty, should only be set when cloud-provider is external. Currently used to allow node and volume controllers to work for in tree cloud providers.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--feature-gates mapStringBool</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">A set of key=value pairs that describe feature gates for alpha/experimental features. Options are:<br/>APIListChunking=true|false (BETA - default=true)<br/>APIResponseCompression=true|false (ALPHA - default=false)<br/>AllAlpha=true|false (ALPHA - default=false)<br/>AppArmor=true|false (BETA - default=true)<br/>AttachVolumeLimit=true|false (BETA - default=true)<br/>BalanceAttachedNodeVolumes=true|false (ALPHA - default=false)<br/>BlockVolume=true|false (BETA - default=true)<br/>BoundServiceAccountTokenVolume=true|false (ALPHA - default=false)<br/>CPUManager=true|false (BETA - default=true)<br/>CRIContainerLogRotation=true|false (BETA - default=true)<br/>CSIBlockVolume=true|false (ALPHA - default=false)<br/>CSIDriverRegistry=true|false (ALPHA - default=false)<br/>CSINodeInfo=true|false (ALPHA - default=false)<br/>CustomCPUCFSQuotaPeriod=true|false (ALPHA - default=false)<br/>CustomPodDNS=true|false (BETA - default=true)<br/>CustomResourceSubresources=true|false (BETA - default=true)<br/>CustomResourceValidation=true|false (BETA - default=true)<br/>CustomResourceWebhookConversion=true|false (ALPHA - default=false)<br/>DebugContainers=true|false (ALPHA - default=false)<br/>DevicePlugins=true|false (BETA - default=true)<br/>DryRun=true|false (BETA - default=true)<br/>DynamicAuditing=true|false (ALPHA - default=false)<br/>DynamicKubeletConfig=true|false (BETA - default=true)<br/>EnableEquivalenceClassCache=true|false (ALPHA - default=false)<br/>ExpandInUsePersistentVolumes=true|false (ALPHA - default=false)<br/>ExpandPersistentVolumes=true|false (BETA - default=true)<br/>ExperimentalCriticalPodAnnotation=true|false (ALPHA - default=false)<br/>ExperimentalHostUserNamespaceDefaulting=true|false (BETA - default=false)<br/>HugePages=true|false (BETA - default=true)<br/>HyperVContainer=true|false (ALPHA - default=false)<br/>Initializers=true|false (ALPHA - default=false)<br/>KubeletPodResources=true|false (ALPHA - default=false)<br/>LocalStorageCapacityIsolation=true|false (BETA - default=true)<br/>LocalStorageCapacityIsolationFSQuotaMonitoring=true|false (ALPHA - default=false)<br/>MountContainers=true|false (ALPHA - default=false)<br/>NodeLease=true|false (ALPHA - default=false)<br/>PersistentLocalVolumes=true|false (BETA - default=true)<br/>PodPriority=true|false (BETA - default=true)<br/>PodReadinessGates=true|false (BETA - default=true)<br/>PodShareProcessNamespace=true|false (BETA - default=true)<br/>ProcMountType=true|false (ALPHA - default=false)<br/>QOSReserved=true|false (ALPHA - default=false)<br/>ResourceLimitsPriorityFunction=true|false (ALPHA - default=false)<br/>ResourceQuotaScopeSelectors=true|false (BETA - default=true)<br/>RotateKubeletClientCertificate=true|false (BETA - default=true)<br/>RotateKubeletServerCertificate=true|false (BETA - default=true)<br/>RunAsGroup=true|false (ALPHA - default=false)<br/>RuntimeClass=true|false (ALPHA - default=false)<br/>SCTPSupport=true|false (ALPHA - default=false)<br/>ScheduleDaemonSetPods=true|false (BETA - default=true)<br/>ServiceNodeExclusion=true|false (ALPHA - default=false)<br/>StreamingProxyRedirects=true|false (BETA - default=true)<br/>SupportPodPidsLimit=true|false (ALPHA - default=false)<br/>Sysctls=true|false (BETA - default=true)<br/>TTLAfterFinished=true|false (ALPHA - default=false)<br/>TaintBasedEvictions=true|false (BETA - default=true)<br/>TaintNodesByCondition=true|false (BETA - default=true)<br/>TokenRequest=true|false (BETA - default=true)<br/>TokenRequestProjection=true|false (BETA - default=true)<br/>ValidateProxyRedirects=true|false (ALPHA - default=false)<br/>VolumeSnapshotDataSource=true|false (ALPHA - default=false)<br/>VolumeSubpathEnvExpansion=true|false (ALPHA - default=false)</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--flex-volume-plugin-dir string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "/usr/libexec/kubernetes/kubelet-plugins/volume/exec/"</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Full path of the directory in which the flex volume plugin should search for additional third party volume plugins.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">-h, --help</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">help for kube-controller-manager</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--horizontal-pod-autoscaler-cpu-initialization-period duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 5m0s</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The period after pod start when CPU samples might be skipped.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--horizontal-pod-autoscaler-downscale-stabilization duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 5m0s</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The period for which autoscaler will look backwards and not scale down below any recommendation it made during that period.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--horizontal-pod-autoscaler-initial-readiness-delay duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 30s</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The period after pod start during which readiness changes will be treated as initial readiness.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--horizontal-pod-autoscaler-sync-period duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 15s</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The period for syncing the number of pods in horizontal pod autoscaler.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--horizontal-pod-autoscaler-tolerance float&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 0.1</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The minimum change (from 1.0) in the desired-to-actual metrics ratio for the horizontal pod autoscaler to consider scaling.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--http2-max-streams-per-connection int</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The limit that the server gives to clients for the maximum number of streams in an HTTP/2 connection. Zero means to use golang's default.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--kube-api-burst int32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 30</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Burst to use while talking with kubernetes apiserver.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--kube-api-content-type string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "application/vnd.kubernetes.protobuf"</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Content type of requests sent to apiserver.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--kube-api-qps float32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 20</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">QPS to use while talking with kubernetes apiserver.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--kubeconfig string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Path to kubeconfig file with authorization and master location information.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--large-cluster-size-threshold int32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 50</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Number of nodes from which NodeController treats the cluster as large for the eviction logic purposes. --secondary-node-eviction-rate is implicitly overridden to 0 for clusters this size or smaller.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--leader-elect&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: true</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Start a leader election client and gain leadership before executing the main loop. Enable this when running replicated components for high availability.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--leader-elect-lease-duration duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 15s</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The duration that non-leader candidates will wait after observing a leadership renewal until attempting to acquire leadership of a led but unrenewed leader slot. This is effectively the maximum duration that a leader can be stopped before it is replaced by another candidate. This is only applicable if leader election is enabled.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--leader-elect-renew-deadline duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 10s</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The interval between attempts by the acting master to renew a leadership slot before it stops leading. This must be less than or equal to the lease duration. This is only applicable if leader election is enabled.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--leader-elect-resource-lock endpoints&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "endpoints"</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The type of resource object that is used for locking during leader election. Supported options are endpoints (default) and `configmaps`.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--leader-elect-retry-period duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 2s</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The duration the clients should wait between attempting acquisition and renewal of a leadership. This is only applicable if leader election is enabled.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--log-backtrace-at traceLocation&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: :0</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">when logging hits line file:N, emit a stack trace</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--log-dir string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">If non-empty, write log files in this directory</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--log-file string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">If non-empty, use this log file</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--log-flush-frequency duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 5s</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Maximum number of seconds between log flushes</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--logtostderr&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: true</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">log to standard error instead of files</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--master string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The address of the Kubernetes API server (overrides any value in kubeconfig).</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--min-resync-period duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 12h0m0s</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The resync period in reflectors will be random between MinResyncPeriod and 2*MinResyncPeriod.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--namespace-sync-period duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 5m0s</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The period for syncing namespace life-cycle updates</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--node-cidr-mask-size int32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 24</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Mask size for node cidr in cluster.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--node-eviction-rate float32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 0.1</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Number of nodes per second on which pods are deleted in case of node failure when a zone is healthy (see --unhealthy-zone-threshold for definition of healthy/unhealthy). Zone refers to entire cluster in non-multizone clusters.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--node-monitor-grace-period duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 40s</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Amount of time which we allow running Node to be unresponsive before marking it unhealthy. Must be N times more than kubelet's nodeStatusUpdateFrequency, where N means number of retries allowed for kubelet to post node status.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--node-monitor-period duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 5s</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The period for syncing NodeStatus in NodeController.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--node-startup-grace-period duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 1m0s</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Amount of time which we allow starting Node to be unresponsive before marking it unhealthy.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--pod-eviction-timeout duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 5m0s</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The grace period for deleting pods on failed nodes.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--profiling</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Enable profiling via web interface host:port/debug/pprof/</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--pv-recycler-increment-timeout-nfs int32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 30</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">the increment of time added per Gi to ActiveDeadlineSeconds for an NFS scrubber pod</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--pv-recycler-minimum-timeout-hostpath int32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 60</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The minimum ActiveDeadlineSeconds to use for a HostPath Recycler pod.  This is for development and testing only and will not work in a multi-node cluster.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--pv-recycler-minimum-timeout-nfs int32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 300</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The minimum ActiveDeadlineSeconds to use for an NFS Recycler pod</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--pv-recycler-pod-template-filepath-hostpath string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The file path to a pod definition used as a template for HostPath persistent volume recycling. This is for development and testing only and will not work in a multi-node cluster.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--pv-recycler-pod-template-filepath-nfs string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The file path to a pod definition used as a template for NFS persistent volume recycling</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--pv-recycler-timeout-increment-hostpath int32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 30</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">the increment of time added per Gi to ActiveDeadlineSeconds for a HostPath scrubber pod.  This is for development and testing only and will not work in a multi-node cluster.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--pvclaimbinder-sync-period duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 15s</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The period for syncing persistent volumes and persistent volume claims</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--requestheader-allowed-names stringSlice</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">List of client certificate common names to allow to provide usernames in headers specified by --requestheader-username-headers. If empty, any client certificate validated by the authorities in --requestheader-client-ca-file is allowed.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--requestheader-client-ca-file string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Root certificate bundle to use to verify client certificates on incoming requests before trusting usernames in headers specified by --requestheader-username-headers. WARNING: generally do not depend on authorization being already done for incoming requests.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--requestheader-extra-headers-prefix stringSlice&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: [x-remote-extra-]</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">List of request header prefixes to inspect. X-Remote-Extra- is suggested.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--requestheader-group-headers stringSlice&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: [x-remote-group]</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">List of request headers to inspect for groups. X-Remote-Group is suggested.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--requestheader-username-headers stringSlice&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: [x-remote-user]</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">List of request headers to inspect for usernames. X-Remote-User is common.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--resource-quota-sync-period duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 5m0s</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The period for syncing quota usage status in the system</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--root-ca-file string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">If set, this root certificate authority will be included in service account's token secret. This must be a valid PEM-encoded CA bundle.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--route-reconciliation-period duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 10s</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The period for reconciling routes created for Nodes by cloud provider.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--secondary-node-eviction-rate float32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 0.01</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Number of nodes per second on which pods are deleted in case of node failure when a zone is unhealthy (see --unhealthy-zone-threshold for definition of healthy/unhealthy). Zone refers to entire cluster in non-multizone clusters. This value is implicitly overridden to 0 if the cluster size is smaller than --large-cluster-size-threshold.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--secure-port int&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 10257</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The port on which to serve HTTPS with authentication and authorization.If 0, don't serve HTTPS at all.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--service-account-private-key-file string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Filename containing a PEM-encoded private RSA or ECDSA key used to sign service account tokens.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--service-cluster-ip-range string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">CIDR Range for Services in cluster. Requires --allocate-node-cidrs to be true</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--skip-headers</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">If true, avoid header prefixes in the log messages</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--stderrthreshold severity&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 2</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">logs at or above this threshold go to stderr</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--terminated-pod-gc-threshold int32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 12500</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Number of terminated pods that can exist before the terminated pod garbage collector starts deleting terminated pods. If &lt;= 0, the terminated pod garbage collector is disabled.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--tls-cert-file string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">File containing the default x509 Certificate for HTTPS. (CA cert, if any, concatenated after server cert). If HTTPS serving is enabled, and --tls-cert-file and --tls-private-key-file are not provided, a self-signed certificate and key are generated for the public address and saved to the directory specified by --cert-dir.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--tls-cipher-suites stringSlice</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Comma-separated list of cipher suites for the server. If omitted, the default Go cipher suites will be use.  Possible values: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_RC4_128_SHA,TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_RC4_128_SHA,TLS_RSA_WITH_3DES_EDE_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_128_GCM_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_RC4_128_SHA</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--tls-min-version string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Minimum TLS version supported. Possible values: VersionTLS10, VersionTLS11, VersionTLS12</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--tls-private-key-file string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">File containing the default x509 private key matching --tls-cert-file.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--tls-sni-cert-key namedCertKey&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: []</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">A pair of x509 certificate and private key file paths, optionally suffixed with a list of domain patterns which are fully qualified domain names, possibly with prefixed wildcard segments. If no domain patterns are provided, the names of the certificate are extracted. Non-wildcard matches trump over wildcard matches, explicit domain patterns trump over extracted names. For multiple key/certificate pairs, use the --tls-sni-cert-key multiple times. Examples: "example.crt,example.key" or "foo.crt,foo.key:*.foo.com,foo.com".</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--unhealthy-zone-threshold float32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 0.55</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Fraction of Nodes in a zone which needs to be not Ready (minimum 3) for zone to be treated as unhealthy. </td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--use-service-account-credentials</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">If true, use individual service account credentials for each controller.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">-v, --v Level</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">number for the log level verbosity</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--version version[=true]</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Print version information and quit</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--vmodule moduleSpec</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">comma-separated list of pattern=N settings for file-filtered logging</td>
-    </tr>
-
-  </tbody>
-</table>
-
-
-

content/en/docs/reference/command-line-tools-reference/kube-proxy.md.orig

@@ -1,317 +0,0 @@
----
-title: kube-proxy
-notitle: true
----
-## kube-proxy
-
-
-
-### Synopsis
-
-
-The Kubernetes network proxy runs on each node. This
-reflects services as defined in the Kubernetes API on each node and can do simple
-TCP, UDP, and SCTP stream forwarding or round robin TCP, UDP, and SCTP forwarding across a set of backends.
-Service cluster IPs and ports are currently found through Docker-links-compatible
-environment variables specifying ports opened by the service proxy. There is an optional
-addon that provides cluster DNS for these cluster IPs. The user must create a service
-with the apiserver API to configure the proxy.
-
-```
-kube-proxy [flags]
-```
-
-### Options
-
-<table style="width: 100%; table-layout: fixed;">
-  <colgroup>
-    <col span="1" style="width: 10px;" />
-    <col span="1" />
-  </colgroup>
-  <tbody>
-
-    <tr>
-      <td colspan="2">--azure-container-registry-config string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Path to the file containing Azure container registry configuration information.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--bind-address 0.0.0.0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 0.0.0.0</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The IP address for the proxy server to serve on (set to 0.0.0.0 for all IPv4 interfaces and `::` for all IPv6 interfaces)</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--cleanup</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">If true cleanup iptables and ipvs rules and exit.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--cleanup-ipvs&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: true</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">If true make kube-proxy cleanup ipvs rules before running.  Default is true</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--cluster-cidr string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The CIDR range of pods in the cluster. When configured, traffic sent to a Service cluster IP from outside this range will be masqueraded and traffic sent from pods to an external LoadBalancer IP will be directed to the respective cluster IP instead</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--config string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The path to the configuration file.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--config-sync-period duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 15m0s</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">How often configuration from the apiserver is refreshed.  Must be greater than 0.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--conntrack-max-per-core int32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 32768</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Maximum number of NAT connections to track per CPU core (0 to leave the limit as-is and ignore conntrack-min).</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--conntrack-min int32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 131072</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Minimum number of conntrack entries to allocate, regardless of conntrack-max-per-core (set conntrack-max-per-core=0 to leave the limit as-is).</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--conntrack-tcp-timeout-close-wait duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 1h0m0s</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">NAT timeout for TCP connections in the CLOSE_WAIT state</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--conntrack-tcp-timeout-established duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 24h0m0s</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Idle timeout for established TCP connections (0 to leave as-is)</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--feature-gates mapStringBool</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">A set of key=value pairs that describe feature gates for alpha/experimental features. Options are:<br/>APIListChunking=true|false (BETA - default=true)<br/>APIResponseCompression=true|false (ALPHA - default=false)<br/>AllAlpha=true|false (ALPHA - default=false)<br/>AppArmor=true|false (BETA - default=true)<br/>AttachVolumeLimit=true|false (BETA - default=true)<br/>BalanceAttachedNodeVolumes=true|false (ALPHA - default=false)<br/>BlockVolume=true|false (BETA - default=true)<br/>BoundServiceAccountTokenVolume=true|false (ALPHA - default=false)<br/>CPUManager=true|false (BETA - default=true)<br/>CRIContainerLogRotation=true|false (BETA - default=true)<br/>CSIBlockVolume=true|false (ALPHA - default=false)<br/>CSIDriverRegistry=true|false (ALPHA - default=false)<br/>CSINodeInfo=true|false (ALPHA - default=false)<br/>CustomCPUCFSQuotaPeriod=true|false (ALPHA - default=false)<br/>CustomPodDNS=true|false (BETA - default=true)<br/>CustomResourceSubresources=true|false (BETA - default=true)<br/>CustomResourceValidation=true|false (BETA - default=true)<br/>CustomResourceWebhookConversion=true|false (ALPHA - default=false)<br/>DebugContainers=true|false (ALPHA - default=false)<br/>DevicePlugins=true|false (BETA - default=true)<br/>DryRun=true|false (BETA - default=true)<br/>DynamicAuditing=true|false (ALPHA - default=false)<br/>DynamicKubeletConfig=true|false (BETA - default=true)<br/>EnableEquivalenceClassCache=true|false (ALPHA - default=false)<br/>ExpandInUsePersistentVolumes=true|false (ALPHA - default=false)<br/>ExpandPersistentVolumes=true|false (BETA - default=true)<br/>ExperimentalCriticalPodAnnotation=true|false (ALPHA - default=false)<br/>ExperimentalHostUserNamespaceDefaulting=true|false (BETA - default=false)<br/>HugePages=true|false (BETA - default=true)<br/>HyperVContainer=true|false (ALPHA - default=false)<br/>Initializers=true|false (ALPHA - default=false)<br/>KubeletPodResources=true|false (ALPHA - default=false)<br/>LocalStorageCapacityIsolation=true|false (BETA - default=true)<br/>LocalStorageCapacityIsolationFSQuotaMonitoring=true|false (ALPHA - default=false)<br/>MountContainers=true|false (ALPHA - default=false)<br/>NodeLease=true|false (ALPHA - default=false)<br/>PersistentLocalVolumes=true|false (BETA - default=true)<br/>PodPriority=true|false (BETA - default=true)<br/>PodReadinessGates=true|false (BETA - default=true)<br/>PodShareProcessNamespace=true|false (BETA - default=true)<br/>ProcMountType=true|false (ALPHA - default=false)<br/>QOSReserved=true|false (ALPHA - default=false)<br/>ResourceLimitsPriorityFunction=true|false (ALPHA - default=false)<br/>ResourceQuotaScopeSelectors=true|false (BETA - default=true)<br/>RotateKubeletClientCertificate=true|false (BETA - default=true)<br/>RotateKubeletServerCertificate=true|false (BETA - default=true)<br/>RunAsGroup=true|false (ALPHA - default=false)<br/>RuntimeClass=true|false (ALPHA - default=false)<br/>SCTPSupport=true|false (ALPHA - default=false)<br/>ScheduleDaemonSetPods=true|false (BETA - default=true)<br/>ServiceNodeExclusion=true|false (ALPHA - default=false)<br/>StreamingProxyRedirects=true|false (BETA - default=true)<br/>SupportPodPidsLimit=true|false (ALPHA - default=false)<br/>Sysctls=true|false (BETA - default=true)<br/>TTLAfterFinished=true|false (ALPHA - default=false)<br/>TaintBasedEvictions=true|false (BETA - default=true)<br/>TaintNodesByCondition=true|false (BETA - default=true)<br/>TokenRequest=true|false (BETA - default=true)<br/>TokenRequestProjection=true|false (BETA - default=true)<br/>ValidateProxyRedirects=true|false (ALPHA - default=false)<br/>VolumeSnapshotDataSource=true|false (ALPHA - default=false)<br/>VolumeSubpathEnvExpansion=true|false (ALPHA - default=false)</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--healthz-bind-address 0.0.0.0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 0.0.0.0:10256</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The IP address for the health check server to serve on (set to 0.0.0.0 for all IPv4 interfaces and `::` for all IPv6 interfaces)</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--healthz-port int32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 10256</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The port to bind the health check server. Use 0 to disable.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">-h, --help</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">help for kube-proxy</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--hostname-override string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">If non-empty, will use this string as identification instead of the actual hostname.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--iptables-masquerade-bit int32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 14</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">If using the pure iptables proxy, the bit of the fwmark space to mark packets requiring SNAT with.  Must be within the range [0, 31].</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--iptables-min-sync-period duration</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The minimum interval of how often the iptables rules can be refreshed as endpoints and services change (e.g. '5s', '1m', '2h22m').</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--iptables-sync-period duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 30s</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The maximum interval of how often iptables rules are refreshed (e.g. '5s', '1m', '2h22m').  Must be greater than 0.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--ipvs-exclude-cidrs stringSlice</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">A comma-separated list of CIDR's which the ipvs proxier should not touch when cleaning up IPVS rules.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--ipvs-min-sync-period duration</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The minimum interval of how often the ipvs rules can be refreshed as endpoints and services change (e.g. '5s', '1m', '2h22m').</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--ipvs-scheduler string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The ipvs scheduler type when proxy mode is ipvs</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--ipvs-sync-period duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 30s</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The maximum interval of how often ipvs rules are refreshed (e.g. '5s', '1m', '2h22m').  Must be greater than 0.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--kube-api-burst int32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 10</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Burst to use while talking with kubernetes apiserver</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--kube-api-content-type string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "application/vnd.kubernetes.protobuf"</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Content type of requests sent to apiserver.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--kube-api-qps float32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 5</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">QPS to use while talking with kubernetes apiserver</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--kubeconfig string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Path to kubeconfig file with authorization information (the master location is set by the master flag).</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--log-flush-frequency duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 5s</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Maximum number of seconds between log flushes</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--masquerade-all</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">If using the pure iptables proxy, SNAT all traffic sent via Service cluster IPs (this not commonly needed)</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--master string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The address of the Kubernetes API server (overrides any value in kubeconfig)</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--metrics-bind-address 0.0.0.0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 127.0.0.1:10249</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The IP address for the metrics server to serve on (set to 0.0.0.0 for all IPv4 interfaces and `::` for all IPv6 interfaces)</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--metrics-port int32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 10249</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The port to bind the metrics server. Use 0 to disable.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--nodeport-addresses stringSlice</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">A string slice of values which specify the addresses to use for NodePorts. Values may be valid IP blocks (e.g. 1.2.3.0/24, 1.2.3.4/32). The default empty string slice ([]) means to use all local addresses.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--oom-score-adj int32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: -999</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The oom-score-adj value for kube-proxy process. Values must be within the range [-1000, 1000]</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--profiling</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">If true enables profiling via web interface on /debug/pprof handler.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--proxy-mode ProxyMode</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Which proxy mode to use: 'userspace' (older) or 'iptables' (faster) or 'ipvs' (experimental). If blank, use the best-available proxy (currently iptables).  If the iptables proxy is selected, regardless of how, but the system's kernel or iptables versions are insufficient, this always falls back to the userspace proxy.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--proxy-port-range port-range</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Range of host ports (beginPort-endPort, single port or beginPort+offset, inclusive) that may be consumed in order to proxy service traffic. If (unspecified, 0, or 0-0) then ports will be randomly chosen.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--udp-timeout duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 250ms</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">How long an idle UDP connection will be kept open (e.g. '250ms', '2s').  Must be greater than 0. Only applicable for proxy-mode=userspace</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--version version[=true]</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Print version information and quit</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--write-config-to string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">If set, write the default configuration values to this file and exit.</td>
-    </tr>
-
-  </tbody>
-</table>
-
-
-

content/en/docs/reference/command-line-tools-reference/kube-scheduler.md.orig

@@ -1,464 +0,0 @@
----
-title: kube-scheduler
-notitle: true
----
-## kube-scheduler
-
-
-
-### Synopsis
-
-
-The Kubernetes scheduler is a policy-rich, topology-aware,
-workload-specific function that significantly impacts availability, performance,
-and capacity. The scheduler needs to take into account individual and collective
-resource requirements, quality of service requirements, hardware/software/policy
-constraints, affinity and anti-affinity specifications, data locality, inter-workload
-interference, deadlines, and so on. Workload-specific requirements will be exposed
-through the API as necessary.
-
-```
-kube-scheduler [flags]
-```
-
-### Options
-
-<table style="width: 100%; table-layout: fixed;">
-  <colgroup>
-    <col span="1" style="width: 10px;" />
-    <col span="1" />
-  </colgroup>
-  <tbody>
-
-    <tr>
-      <td colspan="2">--address string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "0.0.0.0"</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">DEPRECATED: the IP address on which to listen for the --port port (set to 0.0.0.0 for all IPv4 interfaces and :: for all IPv6 interfaces). See --bind-address instead.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--algorithm-provider string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">DEPRECATED: the scheduling algorithm provider to use, one of: ClusterAutoscalerProvider | DefaultProvider</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--alsologtostderr</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">log to standard error as well as files</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--authentication-kubeconfig string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">kubeconfig file pointing at the 'core' kubernetes server with enough rights to create tokenaccessreviews.authentication.k8s.io. This is optional. If empty, all token requests are considered to be anonymous and no client CA is looked up in the cluster.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--authentication-skip-lookup</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">If false, the authentication-kubeconfig will be used to lookup missing authentication configuration from the cluster.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--authentication-token-webhook-cache-ttl duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 10s</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The duration to cache responses from the webhook token authenticator.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--authentication-tolerate-lookup-failure&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: true</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">If true, failures to look up missing authentication configuration from the cluster are not considered fatal. Note that this can result in authentication that treats all requests as anonymous.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--authorization-always-allow-paths stringSlice&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: [/healthz]</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">A list of HTTP paths to skip during authorization, i.e. these are authorized without contacting the 'core' kubernetes server.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--authorization-kubeconfig string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">kubeconfig file pointing at the 'core' kubernetes server with enough rights to create subjectaccessreviews.authorization.k8s.io. This is optional. If empty, all requests not skipped by authorization are forbidden.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--authorization-webhook-cache-authorized-ttl duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 10s</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The duration to cache 'authorized' responses from the webhook authorizer.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--authorization-webhook-cache-unauthorized-ttl duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 10s</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The duration to cache 'unauthorized' responses from the webhook authorizer.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--azure-container-registry-config string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Path to the file containing Azure container registry configuration information.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--bind-address ip&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 0.0.0.0</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The IP address on which to listen for the --secure-port port. The associated interface(s) must be reachable by the rest of the cluster, and by CLI/web clients. If blank, all interfaces will be used (0.0.0.0 for all IPv4 interfaces and :: for all IPv6 interfaces).</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--cert-dir string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The directory where the TLS certs are located. If --tls-cert-file and --tls-private-key-file are provided, this flag will be ignored.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--client-ca-file string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">If set, any request presenting a client certificate signed by one of the authorities in the client-ca-file is authenticated with an identity corresponding to the CommonName of the client certificate.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--config string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The path to the configuration file. Flags override values in this file.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--contention-profiling</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">DEPRECATED: enable lock contention profiling, if profiling is enabled</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--feature-gates mapStringBool</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">A set of key=value pairs that describe feature gates for alpha/experimental features. Options are:<br/>APIListChunking=true|false (BETA - default=true)<br/>APIResponseCompression=true|false (ALPHA - default=false)<br/>AllAlpha=true|false (ALPHA - default=false)<br/>AppArmor=true|false (BETA - default=true)<br/>AttachVolumeLimit=true|false (BETA - default=true)<br/>BalanceAttachedNodeVolumes=true|false (ALPHA - default=false)<br/>BlockVolume=true|false (BETA - default=true)<br/>BoundServiceAccountTokenVolume=true|false (ALPHA - default=false)<br/>CPUManager=true|false (BETA - default=true)<br/>CRIContainerLogRotation=true|false (BETA - default=true)<br/>CSIBlockVolume=true|false (ALPHA - default=false)<br/>CSIDriverRegistry=true|false (ALPHA - default=false)<br/>CSINodeInfo=true|false (ALPHA - default=false)<br/>CustomCPUCFSQuotaPeriod=true|false (ALPHA - default=false)<br/>CustomPodDNS=true|false (BETA - default=true)<br/>CustomResourceSubresources=true|false (BETA - default=true)<br/>CustomResourceValidation=true|false (BETA - default=true)<br/>CustomResourceWebhookConversion=true|false (ALPHA - default=false)<br/>DebugContainers=true|false (ALPHA - default=false)<br/>DevicePlugins=true|false (BETA - default=true)<br/>DryRun=true|false (BETA - default=true)<br/>DynamicAuditing=true|false (ALPHA - default=false)<br/>DynamicKubeletConfig=true|false (BETA - default=true)<br/>EnableEquivalenceClassCache=true|false (ALPHA - default=false)<br/>ExpandInUsePersistentVolumes=true|false (ALPHA - default=false)<br/>ExpandPersistentVolumes=true|false (BETA - default=true)<br/>ExperimentalCriticalPodAnnotation=true|false (ALPHA - default=false)<br/>ExperimentalHostUserNamespaceDefaulting=true|false (BETA - default=false)<br/>HugePages=true|false (BETA - default=true)<br/>HyperVContainer=true|false (ALPHA - default=false)<br/>Initializers=true|false (ALPHA - default=false)<br/>KubeletPodResources=true|false (ALPHA - default=false)<br/>LocalStorageCapacityIsolation=true|false (BETA - default=true)<br/>LocalStorageCapacityIsolationFSQuotaMonitoring=true|false (ALPHA - default=false)<br/>MountContainers=true|false (ALPHA - default=false)<br/>NodeLease=true|false (ALPHA - default=false)<br/>PersistentLocalVolumes=true|false (BETA - default=true)<br/>PodPriority=true|false (BETA - default=true)<br/>PodReadinessGates=true|false (BETA - default=true)<br/>PodShareProcessNamespace=true|false (BETA - default=true)<br/>ProcMountType=true|false (ALPHA - default=false)<br/>QOSReserved=true|false (ALPHA - default=false)<br/>ResourceLimitsPriorityFunction=true|false (ALPHA - default=false)<br/>ResourceQuotaScopeSelectors=true|false (BETA - default=true)<br/>RotateKubeletClientCertificate=true|false (BETA - default=true)<br/>RotateKubeletServerCertificate=true|false (BETA - default=true)<br/>RunAsGroup=true|false (ALPHA - default=false)<br/>RuntimeClass=true|false (ALPHA - default=false)<br/>SCTPSupport=true|false (ALPHA - default=false)<br/>ScheduleDaemonSetPods=true|false (BETA - default=true)<br/>ServiceNodeExclusion=true|false (ALPHA - default=false)<br/>StreamingProxyRedirects=true|false (BETA - default=true)<br/>SupportPodPidsLimit=true|false (ALPHA - default=false)<br/>Sysctls=true|false (BETA - default=true)<br/>TTLAfterFinished=true|false (ALPHA - default=false)<br/>TaintBasedEvictions=true|false (BETA - default=true)<br/>TaintNodesByCondition=true|false (BETA - default=true)<br/>TokenRequest=true|false (BETA - default=true)<br/>TokenRequestProjection=true|false (BETA - default=true)<br/>ValidateProxyRedirects=true|false (ALPHA - default=false)<br/>VolumeSnapshotDataSource=true|false (ALPHA - default=false)<br/>VolumeSubpathEnvExpansion=true|false (ALPHA - default=false)</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">-h, --help</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">help for kube-scheduler</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--http2-max-streams-per-connection int</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The limit that the server gives to clients for the maximum number of streams in an HTTP/2 connection. Zero means to use golang's default.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--kube-api-burst int32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 100</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">DEPRECATED: burst to use while talking with kubernetes apiserver</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--kube-api-content-type string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "application/vnd.kubernetes.protobuf"</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">DEPRECATED: content type of requests sent to apiserver.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--kube-api-qps float32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 50</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">DEPRECATED: QPS to use while talking with kubernetes apiserver</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--kubeconfig string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">DEPRECATED: path to kubeconfig file with authorization and master location information.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--leader-elect&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: true</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Start a leader election client and gain leadership before executing the main loop. Enable this when running replicated components for high availability.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--leader-elect-lease-duration duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 15s</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The duration that non-leader candidates will wait after observing a leadership renewal until attempting to acquire leadership of a led but unrenewed leader slot. This is effectively the maximum duration that a leader can be stopped before it is replaced by another candidate. This is only applicable if leader election is enabled.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--leader-elect-renew-deadline duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 10s</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The interval between attempts by the acting master to renew a leadership slot before it stops leading. This must be less than or equal to the lease duration. This is only applicable if leader election is enabled.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--leader-elect-resource-lock endpoints&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "endpoints"</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The type of resource object that is used for locking during leader election. Supported options are endpoints (default) and `configmaps`.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--leader-elect-retry-period duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 2s</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The duration the clients should wait between attempting acquisition and renewal of a leadership. This is only applicable if leader election is enabled.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--lock-object-name string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "kube-scheduler"</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">DEPRECATED: define the name of the lock object.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--lock-object-namespace string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "kube-system"</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">DEPRECATED: define the namespace of the lock object.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--log-backtrace-at traceLocation&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: :0</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">when logging hits line file:N, emit a stack trace</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--log-dir string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">If non-empty, write log files in this directory</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--log-file string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">If non-empty, use this log file</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--log-flush-frequency duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 5s</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Maximum number of seconds between log flushes</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--logtostderr&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: true</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">log to standard error instead of files</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--master string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The address of the Kubernetes API server (overrides any value in kubeconfig)</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--policy-config-file string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">DEPRECATED: file with scheduler policy configuration. This file is used if policy ConfigMap is not provided or --use-legacy-policy-config=true</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--policy-configmap string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">DEPRECATED: name of the ConfigMap object that contains scheduler's policy configuration. It must exist in the system namespace before scheduler initialization if --use-legacy-policy-config=false. The config must be provided as the value of an element in 'Data' map with the key='policy.cfg'</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--policy-configmap-namespace string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "kube-system"</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">DEPRECATED: the namespace where policy ConfigMap is located. The kube-system namespace will be used if this is not provided or is empty.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--port int&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 10251</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">DEPRECATED: the port on which to serve HTTP insecurely without authentication and authorization. If 0, don't serve HTTPS at all. See --secure-port instead.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--profiling</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">DEPRECATED: enable profiling via web interface host:port/debug/pprof/</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--requestheader-allowed-names stringSlice</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">List of client certificate common names to allow to provide usernames in headers specified by --requestheader-username-headers. If empty, any client certificate validated by the authorities in --requestheader-client-ca-file is allowed.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--requestheader-client-ca-file string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Root certificate bundle to use to verify client certificates on incoming requests before trusting usernames in headers specified by --requestheader-username-headers. WARNING: generally do not depend on authorization being already done for incoming requests.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--requestheader-extra-headers-prefix stringSlice&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: [x-remote-extra-]</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">List of request header prefixes to inspect. X-Remote-Extra- is suggested.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--requestheader-group-headers stringSlice&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: [x-remote-group]</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">List of request headers to inspect for groups. X-Remote-Group is suggested.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--requestheader-username-headers stringSlice&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: [x-remote-user]</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">List of request headers to inspect for usernames. X-Remote-User is common.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--scheduler-name string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "default-scheduler"</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">DEPRECATED: name of the scheduler, used to select which pods will be processed by this scheduler, based on pod's "spec.schedulerName".</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--secure-port int&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 10259</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The port on which to serve HTTPS with authentication and authorization.If 0, don't serve HTTPS at all.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--skip-headers</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">If true, avoid header prefixes in the log messages</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--stderrthreshold severity&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 2</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">logs at or above this threshold go to stderr</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--tls-cert-file string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">File containing the default x509 Certificate for HTTPS. (CA cert, if any, concatenated after server cert). If HTTPS serving is enabled, and --tls-cert-file and --tls-private-key-file are not provided, a self-signed certificate and key are generated for the public address and saved to the directory specified by --cert-dir.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--tls-cipher-suites stringSlice</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Comma-separated list of cipher suites for the server. If omitted, the default Go cipher suites will be use.  Possible values: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_RC4_128_SHA,TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_RC4_128_SHA,TLS_RSA_WITH_3DES_EDE_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_128_GCM_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_RC4_128_SHA</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--tls-min-version string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Minimum TLS version supported. Possible values: VersionTLS10, VersionTLS11, VersionTLS12</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--tls-private-key-file string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">File containing the default x509 private key matching --tls-cert-file.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--tls-sni-cert-key namedCertKey&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: []</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">A pair of x509 certificate and private key file paths, optionally suffixed with a list of domain patterns which are fully qualified domain names, possibly with prefixed wildcard segments. If no domain patterns are provided, the names of the certificate are extracted. Non-wildcard matches trump over wildcard matches, explicit domain patterns trump over extracted names. For multiple key/certificate pairs, use the --tls-sni-cert-key multiple times. Examples: "example.crt,example.key" or "foo.crt,foo.key:*.foo.com,foo.com".</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--use-legacy-policy-config</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">DEPRECATED: when set to true, scheduler will ignore policy ConfigMap and uses policy config file</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">-v, --v Level</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">number for the log level verbosity</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--version version[=true]</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Print version information and quit</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--vmodule moduleSpec</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">comma-separated list of pattern=N settings for file-filtered logging</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--write-config-to string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">If set, write the configuration values to this file and exit.</td>
-    </tr>
-
-  </tbody>
-</table>
-
-
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_renew_all.md.orig

@@ -1,29 +0,0 @@
-
-Renew all available certificates
-
-### Synopsis
-
-Renew all known certificates necessary to run the control plane. Renewals are run unconditionally, regardless of expiration date. Renewals can also be run individually for more control.
-
-```
-kubeadm alpha certs renew all [flags]
-```
-
-### Options
-
-```
-      --cert-dir string     The path where to save the certificates (default "/etc/kubernetes/pki")
-      --config string       Path to a kubeadm configuration file.
-      --csr-dir string      The path to output the CSRs and private keys to
-      --csr-only            Create CSRs instead of generating certificates
-  -h, --help                help for all
-      --kubeconfig string   The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. (default "/etc/kubernetes/admin.conf")
-      --use-api             Use the Kubernetes certificate API to renew certificates
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_renew_all_BACKUP_17211.md

@@ -1,29 +0,0 @@
-
-Renew all available certificates
-
-### Synopsis
-
-Renew all known certificates necessary to run the control plane. Renewals are run unconditionally, regardless of expiration date. Renewals can also be run individually for more control.
-
-```
-kubeadm alpha certs renew all [flags]
-```
-
-### Options
-
-```
-      --cert-dir string     The path where to save the certificates (default "/etc/kubernetes/pki")
-      --config string       Path to a kubeadm configuration file.
-      --csr-dir string      The path to output the CSRs and private keys to
-      --csr-only            Create CSRs instead of generating certificates
-  -h, --help                help for all
-      --kubeconfig string   The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. (default "/etc/kubernetes/admin.conf")
-      --use-api             Use the Kubernetes certificate API to renew certificates
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_renew_all_BASE_17211.md

@@ -1,96 +0,0 @@
-
-renew all available certificates
-
-### Synopsis
-
-
-Renews all known certificates necessary to run the control plan. Renewals are run unconditionally, regardless of expiration date. Renewals can also be run individually for more control.
-
-```
-kubeadm alpha certs renew all [flags]
-```
-
-### 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&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "/etc/kubernetes/pki"</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The path where to save the certificates</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--config string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Path to a kubeadm configuration file.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--csr-dir string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The path to output the CSRs and private keys to</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--csr-only</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Create CSRs instead of generating certificates</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">-h, --help</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">help for all</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--kubeconfig string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "/etc/kubernetes/admin.conf"</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations are searched for an existing KubeConfig file.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--use-api</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Use the Kubernetes certificate API to renew certificates</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;">[EXPERIMENTAL] The path to the 'real' host root filesystem.</td>
-    </tr>
-
-  </tbody>
-</table>
-
-
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_renew_all_LOCAL_17211.md

@@ -1,29 +0,0 @@
-
-Renew all available certificates
-
-### Synopsis
-
-Renew all known certificates necessary to run the control plane. Renewals are run unconditionally, regardless of expiration date. Renewals can also be run individually for more control.
-
-```
-kubeadm alpha certs renew all [flags]
-```
-
-### Options
-
-```
-      --cert-dir string     The path where to save the certificates (default "/etc/kubernetes/pki")
-      --config string       Path to a kubeadm configuration file.
-      --csr-dir string      The path to output the CSRs and private keys to
-      --csr-only            Create CSRs instead of generating certificates
-  -h, --help                help for all
-      --kubeconfig string   The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. (default "/etc/kubernetes/admin.conf")
-      --use-api             Use the Kubernetes certificate API to renew certificates
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_renew_all_REMOTE_17211.md

@@ -1,96 +0,0 @@
-
-renew all available certificates
-
-### Synopsis
-
-
-Renews all known certificates necessary to run the control plane. Renewals are run unconditionally, regardless of expiration date. Renewals can also be run individually for more control.
-
-```
-kubeadm alpha certs renew all [flags]
-```
-
-### 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&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "/etc/kubernetes/pki"</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The path where to save the certificates</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--config string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Path to a kubeadm configuration file.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--csr-dir string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The path to output the CSRs and private keys to</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--csr-only</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Create CSRs instead of generating certificates</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">-h, --help</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">help for all</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--kubeconfig string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "/etc/kubernetes/admin.conf"</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--use-api</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Use the Kubernetes certificate API to renew certificates</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;">[EXPERIMENTAL] The path to the 'real' host root filesystem.</td>
-    </tr>
-
-  </tbody>
-</table>
-
-
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_renew_apiserver-etcd-client.md.orig

@@ -1,35 +0,0 @@
-
-Renew the certificate the apiserver uses to access etcd
-
-### Synopsis
-
-Renew the certificate the apiserver uses to access etcd. 
-
-Renewals run unconditionally, regardless of certificate expiration date; extra attributes such as SANs will be based on the existing file/certificates, there is no need to resupply them. 
-
-Renewal by default tries to use the certificate authority in the local PKI managed by kubeadm; as alternative it is possible to use K8s certificate API for certificate renewal, or as a last option, to generate a CSR request. 
-
-After renewal, in order to make changes effective, is is required to restart control-plane components and eventually re-distribute the renewed certificate in case the file is used elsewhere.
-
-```
-kubeadm alpha certs renew apiserver-etcd-client [flags]
-```
-
-### Options
-
-```
-      --cert-dir string     The path where to save the certificates (default "/etc/kubernetes/pki")
-      --config string       Path to a kubeadm configuration file.
-      --csr-dir string      The path to output the CSRs and private keys to
-      --csr-only            Create CSRs instead of generating certificates
-  -h, --help                help for apiserver-etcd-client
-      --kubeconfig string   The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. (default "/etc/kubernetes/admin.conf")
-      --use-api             Use the Kubernetes certificate API to renew certificates
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_renew_apiserver-kubelet-client.md.orig

@@ -1,35 +0,0 @@
-
-Renew the certificate for the API server to connect to kubelet
-
-### Synopsis
-
-Renew the certificate for the API server to connect to kubelet. 
-
-Renewals run unconditionally, regardless of certificate expiration date; extra attributes such as SANs will be based on the existing file/certificates, there is no need to resupply them. 
-
-Renewal by default tries to use the certificate authority in the local PKI managed by kubeadm; as alternative it is possible to use K8s certificate API for certificate renewal, or as a last option, to generate a CSR request. 
-
-After renewal, in order to make changes effective, is is required to restart control-plane components and eventually re-distribute the renewed certificate in case the file is used elsewhere.
-
-```
-kubeadm alpha certs renew apiserver-kubelet-client [flags]
-```
-
-### Options
-
-```
-      --cert-dir string     The path where to save the certificates (default "/etc/kubernetes/pki")
-      --config string       Path to a kubeadm configuration file.
-      --csr-dir string      The path to output the CSRs and private keys to
-      --csr-only            Create CSRs instead of generating certificates
-  -h, --help                help for apiserver-kubelet-client
-      --kubeconfig string   The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. (default "/etc/kubernetes/admin.conf")
-      --use-api             Use the Kubernetes certificate API to renew certificates
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_renew_apiserver.md.orig

@@ -1,35 +0,0 @@
-
-Renew the certificate for serving the Kubernetes API
-
-### Synopsis
-
-Renew the certificate for serving the Kubernetes API. 
-
-Renewals run unconditionally, regardless of certificate expiration date; extra attributes such as SANs will be based on the existing file/certificates, there is no need to resupply them. 
-
-Renewal by default tries to use the certificate authority in the local PKI managed by kubeadm; as alternative it is possible to use K8s certificate API for certificate renewal, or as a last option, to generate a CSR request. 
-
-After renewal, in order to make changes effective, is is required to restart control-plane components and eventually re-distribute the renewed certificate in case the file is used elsewhere.
-
-```
-kubeadm alpha certs renew apiserver [flags]
-```
-
-### Options
-
-```
-      --cert-dir string     The path where to save the certificates (default "/etc/kubernetes/pki")
-      --config string       Path to a kubeadm configuration file.
-      --csr-dir string      The path to output the CSRs and private keys to
-      --csr-only            Create CSRs instead of generating certificates
-  -h, --help                help for apiserver
-      --kubeconfig string   The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. (default "/etc/kubernetes/admin.conf")
-      --use-api             Use the Kubernetes certificate API to renew certificates
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_renew_etcd-healthcheck-client.md.orig

@@ -1,35 +0,0 @@
-
-Renew the certificate for liveness probes to healtcheck etcd
-
-### Synopsis
-
-Renew the certificate for liveness probes to healtcheck etcd. 
-
-Renewals run unconditionally, regardless of certificate expiration date; extra attributes such as SANs will be based on the existing file/certificates, there is no need to resupply them. 
-
-Renewal by default tries to use the certificate authority in the local PKI managed by kubeadm; as alternative it is possible to use K8s certificate API for certificate renewal, or as a last option, to generate a CSR request. 
-
-After renewal, in order to make changes effective, is is required to restart control-plane components and eventually re-distribute the renewed certificate in case the file is used elsewhere.
-
-```
-kubeadm alpha certs renew etcd-healthcheck-client [flags]
-```
-
-### Options
-
-```
-      --cert-dir string     The path where to save the certificates (default "/etc/kubernetes/pki")
-      --config string       Path to a kubeadm configuration file.
-      --csr-dir string      The path to output the CSRs and private keys to
-      --csr-only            Create CSRs instead of generating certificates
-  -h, --help                help for etcd-healthcheck-client
-      --kubeconfig string   The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. (default "/etc/kubernetes/admin.conf")
-      --use-api             Use the Kubernetes certificate API to renew certificates
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_renew_etcd-peer.md.orig

@@ -1,35 +0,0 @@
-
-Renew the certificate for etcd nodes to communicate with each other
-
-### Synopsis
-
-Renew the certificate for etcd nodes to communicate with each other. 
-
-Renewals run unconditionally, regardless of certificate expiration date; extra attributes such as SANs will be based on the existing file/certificates, there is no need to resupply them. 
-
-Renewal by default tries to use the certificate authority in the local PKI managed by kubeadm; as alternative it is possible to use K8s certificate API for certificate renewal, or as a last option, to generate a CSR request. 
-
-After renewal, in order to make changes effective, is is required to restart control-plane components and eventually re-distribute the renewed certificate in case the file is used elsewhere.
-
-```
-kubeadm alpha certs renew etcd-peer [flags]
-```
-
-### Options
-
-```
-      --cert-dir string     The path where to save the certificates (default "/etc/kubernetes/pki")
-      --config string       Path to a kubeadm configuration file.
-      --csr-dir string      The path to output the CSRs and private keys to
-      --csr-only            Create CSRs instead of generating certificates
-  -h, --help                help for etcd-peer
-      --kubeconfig string   The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. (default "/etc/kubernetes/admin.conf")
-      --use-api             Use the Kubernetes certificate API to renew certificates
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_renew_etcd-server.md.orig

@@ -1,35 +0,0 @@
-
-Renew the certificate for serving etcd
-
-### Synopsis
-
-Renew the certificate for serving etcd. 
-
-Renewals run unconditionally, regardless of certificate expiration date; extra attributes such as SANs will be based on the existing file/certificates, there is no need to resupply them. 
-
-Renewal by default tries to use the certificate authority in the local PKI managed by kubeadm; as alternative it is possible to use K8s certificate API for certificate renewal, or as a last option, to generate a CSR request. 
-
-After renewal, in order to make changes effective, is is required to restart control-plane components and eventually re-distribute the renewed certificate in case the file is used elsewhere.
-
-```
-kubeadm alpha certs renew etcd-server [flags]
-```
-
-### Options
-
-```
-      --cert-dir string     The path where to save the certificates (default "/etc/kubernetes/pki")
-      --config string       Path to a kubeadm configuration file.
-      --csr-dir string      The path to output the CSRs and private keys to
-      --csr-only            Create CSRs instead of generating certificates
-  -h, --help                help for etcd-server
-      --kubeconfig string   The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. (default "/etc/kubernetes/admin.conf")
-      --use-api             Use the Kubernetes certificate API to renew certificates
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_renew_front-proxy-client.md.orig

@@ -1,35 +0,0 @@
-
-Renew the certificate for the front proxy client
-
-### Synopsis
-
-Renew the certificate for the front proxy client. 
-
-Renewals run unconditionally, regardless of certificate expiration date; extra attributes such as SANs will be based on the existing file/certificates, there is no need to resupply them. 
-
-Renewal by default tries to use the certificate authority in the local PKI managed by kubeadm; as alternative it is possible to use K8s certificate API for certificate renewal, or as a last option, to generate a CSR request. 
-
-After renewal, in order to make changes effective, is is required to restart control-plane components and eventually re-distribute the renewed certificate in case the file is used elsewhere.
-
-```
-kubeadm alpha certs renew front-proxy-client [flags]
-```
-
-### Options
-
-```
-      --cert-dir string     The path where to save the certificates (default "/etc/kubernetes/pki")
-      --config string       Path to a kubeadm configuration file.
-      --csr-dir string      The path to output the CSRs and private keys to
-      --csr-only            Create CSRs instead of generating certificates
-  -h, --help                help for front-proxy-client
-      --kubeconfig string   The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. (default "/etc/kubernetes/admin.conf")
-      --use-api             Use the Kubernetes certificate API to renew certificates
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_kubelet_config_download.md.orig

@@ -1,37 +0,0 @@
-
-Download the kubelet configuration from the cluster ConfigMap kubelet-config-1.X, where X is the minor version of the kubelet
-
-### Synopsis
-
-Download the kubelet configuration from a ConfigMap of the form "kubelet-config-1.X" in the cluster, where X is the minor version of the kubelet. Either kubeadm autodetects the kubelet version by exec-ing "kubelet --version" or respects the --kubelet-version parameter. 
-
-Alpha Disclaimer: this command is currently alpha.
-
-```
-kubeadm alpha kubelet config download [flags]
-```
-
-### Examples
-
-```
-  # Download the kubelet configuration from the ConfigMap in the cluster. Autodetect the kubelet version.
-  kubeadm alpha phase kubelet config download
-  
-  # Download the kubelet configuration from the ConfigMap in the cluster. Use a specific desired kubelet version.
-  kubeadm alpha phase kubelet config download --kubelet-version 1.14.0
-```
-
-### Options
-
-```
-  -h, --help                     help for download
-      --kubeconfig string        The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. (default "/etc/kubernetes/admin.conf")
-      --kubelet-version string   The desired version for the kubelet. Defaults to being autodetected from 'kubelet --version'.
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_kubelet_config_enable-dynamic.md.orig

@@ -1,40 +0,0 @@
-
-EXPERIMENTAL: Enable or update dynamic kubelet configuration for a Node
-
-### Synopsis
-
-Enable or update dynamic kubelet configuration for a Node, against the kubelet-config-1.X ConfigMap in the cluster, where X is the minor version of the desired kubelet version. 
-
-WARNING: This feature is still experimental, and disabled by default. Enable only if you know what you are doing, as it may have surprising side-effects at this stage. 
-
-Alpha Disclaimer: this command is currently alpha.
-
-```
-kubeadm alpha kubelet config enable-dynamic [flags]
-```
-
-### Examples
-
-```
-  # Enable dynamic kubelet configuration for a Node.
-  kubeadm alpha phase kubelet enable-dynamic-config --node-name node-1 --kubelet-version 1.14.0
-  
-  WARNING: This feature is still experimental, and disabled by default. Enable only if you know what you are doing, as it
-  may have surprising side-effects at this stage.
-```
-
-### Options
-
-```
-  -h, --help                     help for enable-dynamic
-      --kubeconfig string        The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. (default "/etc/kubernetes/admin.conf")
-      --kubelet-version string   The desired version for the kubelet
-      --node-name string         Name of the node that should enable the dynamic kubelet configuration
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_selfhosting_pivot.md.orig

@@ -1,40 +0,0 @@
-
-Convert a static Pod-hosted control plane into a self-hosted one
-
-### Synopsis
-
-Convert static Pod files for control plane components into self-hosted DaemonSets configured via the Kubernetes API. 
-
-See the documentation for self-hosting limitations. 
-
-Alpha Disclaimer: this command is currently alpha.
-
-```
-kubeadm alpha selfhosting pivot [flags]
-```
-
-### Examples
-
-```
-  # Convert a static Pod-hosted control plane into a self-hosted one.
-  
-  kubeadm alpha phase self-hosting convert-from-staticpods
-```
-
-### Options
-
-```
-      --cert-dir string          The path where certificates are stored (default "/etc/kubernetes/pki")
-      --config string            Path to a kubeadm configuration file.
-  -f, --force                    Pivot the cluster without prompting for confirmation
-  -h, --help                     help for pivot
-      --kubeconfig string        The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. (default "/etc/kubernetes/admin.conf")
-  -s, --store-certs-in-secrets   Enable storing certs in secrets
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_config.md.orig

@@ -1,29 +0,0 @@
-
-Manage configuration for a kubeadm cluster persisted in a ConfigMap in the cluster
-
-### Synopsis
-
-
-There is a ConfigMap in the kube-system namespace called "kubeadm-config" that kubeadm uses to store internal configuration about the
-cluster. kubeadm CLI v1.8.0+ automatically creates this ConfigMap with the config used with 'kubeadm init', but if you
-initialized your cluster using kubeadm v1.7.x or lower, you must use the 'config upload' command to create this
-ConfigMap. This is required so that 'kubeadm upgrade' can configure your upgraded cluster correctly.
-
-
-```
-kubeadm config [flags]
-```
-
-### Options
-
-```
-  -h, --help                help for config
-      --kubeconfig string   The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. (default "/etc/kubernetes/admin.conf")
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_images.md.orig

@@ -1,24 +0,0 @@
-
-Interact with container images used by kubeadm
-
-### Synopsis
-
-Interact with container images used by kubeadm
-
-```
-kubeadm config images [flags]
-```
-
-### Options
-
-```
-  -h, --help   help for images
-```
-
-### Options inherited from parent commands
-
-```
-      --kubeconfig string   The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. (default "/etc/kubernetes/admin.conf")
-      --rootfs string       [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_images_list.md.orig

@@ -1,28 +0,0 @@
-
-Print a list of images kubeadm will use. The configuration file is used in case any images or image repositories are customized
-
-### Synopsis
-
-Print a list of images kubeadm will use. The configuration file is used in case any images or image repositories are customized
-
-```
-kubeadm config images list [flags]
-```
-
-### Options
-
-```
-      --config string               Path to kubeadm config file.
-      --feature-gates string        A set of key=value pairs that describe feature gates for various features. No feature gates are available in this release.
-  -h, --help                        help for list
-      --image-repository string     Choose a container registry to pull control plane images from (default "k8s.gcr.io")
-      --kubernetes-version string   Choose a specific Kubernetes version for the control plane. (default "stable-1")
-```
-
-### Options inherited from parent commands
-
-```
-      --kubeconfig string   The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. (default "/etc/kubernetes/admin.conf")
-      --rootfs string       [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_images_pull.md.orig

@@ -1,29 +0,0 @@
-
-Pull images used by kubeadm
-
-### Synopsis
-
-Pull images used by kubeadm
-
-```
-kubeadm config images pull [flags]
-```
-
-### Options
-
-```
-      --config string               Path to kubeadm config file.
-      --cri-socket string           Path to the CRI socket to connect. If empty kubeadm will try to auto-detect this value; use this option only if you have more than one CRI installed or if you have non-standard CRI socket.
-      --feature-gates string        A set of key=value pairs that describe feature gates for various features. No feature gates are available in this release.
-  -h, --help                        help for pull
-      --image-repository string     Choose a container registry to pull control plane images from (default "k8s.gcr.io")
-      --kubernetes-version string   Choose a specific Kubernetes version for the control plane. (default "stable-1")
-```
-
-### Options inherited from parent commands
-
-```
-      --kubeconfig string   The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. (default "/etc/kubernetes/admin.conf")
-      --rootfs string       [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_migrate.md.orig

@@ -1,41 +0,0 @@
-
-Read an older version of the kubeadm configuration API types from a file, and output the similar config object for the newer version
-
-### Synopsis
-
-
-This command lets you convert configuration objects of older versions to the latest supported version,
-locally in the CLI tool without ever touching anything in the cluster.
-In this version of kubeadm, the following API versions are supported:
-
-- kubeadm.k8s.io/v1beta1
-- kubeadm.k8s.io/v1beta2
-
-Further, kubeadm can only write out config of version "kubeadm.k8s.io/v1beta2", but read both types.
-So regardless of what version you pass to the --old-config parameter here, the API object will be
-read, deserialized, defaulted, converted, validated, and re-serialized when written to stdout or
---new-config if specified.
-
-In other words, the output of this command is what kubeadm actually would read internally if you
-submitted this file to "kubeadm init"
-
-
-```
-kubeadm config migrate [flags]
-```
-
-### Options
-
-```
-  -h, --help                help for migrate
-      --new-config string   Path to the resulting equivalent kubeadm config file using the new API version. Optional, if not specified output will be sent to STDOUT.
-      --old-config string   Path to the kubeadm config file that is using an old API version and should be converted. This flag is mandatory.
-```
-
-### Options inherited from parent commands
-
-```
-      --kubeconfig string   The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. (default "/etc/kubernetes/admin.conf")
-      --rootfs string       [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_print.md.orig

@@ -1,24 +0,0 @@
-
-Print configuration
-
-### Synopsis
-
-This command prints configurations for subcommands provided.
-
-```
-kubeadm config print [flags]
-```
-
-### Options
-
-```
-  -h, --help   help for print
-```
-
-### Options inherited from parent commands
-
-```
-      --kubeconfig string   The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. (default "/etc/kubernetes/admin.conf")
-      --rootfs string       [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_print_init-defaults.md.orig

@@ -1,30 +0,0 @@
-
-Print default init configuration, that can be used for 'kubeadm init'
-
-### Synopsis
-
-
-This command prints objects such as the default init configuration that is used for 'kubeadm init'.
-
-Note that sensitive values like the Bootstrap Token fields are replaced with placeholder values like {"abcdef.0123456789abcdef" "" "nil" <nil> [] []} in order to pass validation but
-not perform the real computation for creating a token.
-
-
-```
-kubeadm config print init-defaults [flags]
-```
-
-### Options
-
-```
-      --component-configs strings   A comma-separated list for component config API objects to print the default values for. Available values: [KubeProxyConfiguration KubeletConfiguration]. If this flag is not set, no component configs will be printed.
-  -h, --help                        help for init-defaults
-```
-
-### Options inherited from parent commands
-
-```
-      --kubeconfig string   The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. (default "/etc/kubernetes/admin.conf")
-      --rootfs string       [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_print_join-defaults.md.orig

@@ -1,30 +0,0 @@
-
-Print default join configuration, that can be used for 'kubeadm join'
-
-### Synopsis
-
-
-This command prints objects such as the default join configuration that is used for 'kubeadm join'.
-
-Note that sensitive values like the Bootstrap Token fields are replaced with placeholder values like {"abcdef.0123456789abcdef" "" "nil" <nil> [] []} in order to pass validation but
-not perform the real computation for creating a token.
-
-
-```
-kubeadm config print join-defaults [flags]
-```
-
-### Options
-
-```
-      --component-configs strings   A comma-separated list for component config API objects to print the default values for. Available values: [KubeProxyConfiguration KubeletConfiguration]. If this flag is not set, no component configs will be printed.
-  -h, --help                        help for join-defaults
-```
-
-### Options inherited from parent commands
-
-```
-      --kubeconfig string   The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. (default "/etc/kubernetes/admin.conf")
-      --rootfs string       [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_upload.md.orig

@@ -1,61 +0,0 @@
-
-Upload configuration about the current state, so that 'kubeadm upgrade' can later know how to configure the upgraded cluster.
-
-### Synopsis
-
-
-Upload configuration about the current state, so that 'kubeadm upgrade' can later know how to configure the upgraded cluster.
-
-```
-kubeadm config upload [flags]
-```
-
-### Options
-
-<table style="width: 100%; table-layout: fixed;">
-  <colgroup>
-    <col span="1" style="width: 10px;" />
-    <col span="1" />
-  </colgroup>
-  <tbody>
-
-    <tr>
-      <td colspan="2">-h, --help</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">help for upload</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">--kubeconfig string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "/etc/kubernetes/admin.conf"</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--rootfs string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">[EXPERIMENTAL] The path to the 'real' host root filesystem.</td>
-    </tr>
-
-  </tbody>
-</table>
-
-
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_upload_from-file.md.orig

@@ -1,74 +0,0 @@
-
-Upload a configuration file to the in-cluster ConfigMap for kubeadm configuration.
-
-### Synopsis
-
-
-
-Using this command, you can upload configuration to the ConfigMap in the cluster using the same config file you gave to 'kubeadm init'.
-If you initialized your cluster using a v1.7.x or lower kubeadm client and used the --config option, you need to run this command with the
-same config file before upgrading to v1.8 using 'kubeadm upgrade'.
-
-The configuration is located in the "kube-system" namespace in the "kubeadm-config" ConfigMap.
-
-
-```
-kubeadm config upload from-file [flags]
-```
-
-### Options
-
-<table style="width: 100%; table-layout: fixed;">
-  <colgroup>
-    <col span="1" style="width: 10px;" />
-    <col span="1" />
-  </colgroup>
-  <tbody>
-
-    <tr>
-      <td colspan="2">--config string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Path to a kubeadm configuration file.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">-h, --help</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">help for from-file</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">--kubeconfig string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "/etc/kubernetes/admin.conf"</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--rootfs string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">[EXPERIMENTAL] The path to the 'real' host root filesystem.</td>
-    </tr>
-
-  </tbody>
-</table>
-
-
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_upload_from-flags.md.orig

@@ -1,144 +0,0 @@
-
-Create the in-cluster configuration file for the first time from using flags.
-
-### Synopsis
-
-
-
-Using this command, you can upload configuration to the ConfigMap in the cluster using the same flags you gave to 'kubeadm init'.
-If you initialized your cluster using a v1.7.x or lower kubeadm client and set certain flags, you need to run this command with the
-same flags before upgrading to v1.8 using 'kubeadm upgrade'.
-
-The configuration is located in the "kube-system" namespace in the "kubeadm-config" ConfigMap.
-
-
-```
-kubeadm config upload from-flags [flags]
-```
-
-### Options
-
-<table style="width: 100%; table-layout: fixed;">
-  <colgroup>
-    <col span="1" style="width: 10px;" />
-    <col span="1" />
-  </colgroup>
-  <tbody>
-
-    <tr>
-      <td colspan="2">--apiserver-advertise-address string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The IP address the API Server will advertise it's listening on. If not set the default network interface will be used.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--apiserver-bind-port int32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 6443</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Port for the API Server to bind to.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--apiserver-cert-extra-sans stringSlice</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Optional extra Subject Alternative Names (SANs) to use for the API Server serving certificate. Can be both IP addresses and DNS names.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--cert-dir string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "/etc/kubernetes/pki"</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The path where to save and store the certificates.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--cri-socket string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Path to the CRI socket to connect. If empty kubeadm will try to auto-detect this value; use this option only if you have more than one CRI installed or if you have non-standard CRI socket.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--feature-gates string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">A set of key=value pairs that describe feature gates for various features. Options are:<br/></td>
-    </tr>
-
-    <tr>
-      <td colspan="2">-h, --help</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">help for from-flags</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--kubernetes-version string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "stable-1"</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Choose a specific Kubernetes version for the control plane.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--node-name string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Specify the node name.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--pod-network-cidr string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Specify range of IP addresses for the pod network. If set, the control plane will automatically allocate CIDRs for every node.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--service-cidr string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "10.96.0.0/12"</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Use alternative range of IP address for service VIPs.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--service-dns-domain string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "cluster.local"</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Use alternative domain for services, e.g. "myorg.internal".</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">--kubeconfig string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "/etc/kubernetes/admin.conf"</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--rootfs string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">[EXPERIMENTAL] The path to the 'real' host root filesystem.</td>
-    </tr>
-
-  </tbody>
-</table>
-
-
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_view.md.orig

@@ -1,28 +0,0 @@
-
-View the kubeadm configuration stored inside the cluster
-
-### Synopsis
-
-
-Using this command, you can view the ConfigMap in the cluster where the configuration for kubeadm is located.
-
-The configuration is located in the "kube-system" namespace in the "kubeadm-config" ConfigMap.
-
-
-```
-kubeadm config view [flags]
-```
-
-### Options
-
-```
-  -h, --help   help for view
-```
-
-### Options inherited from parent commands
-
-```
-      --kubeconfig string   The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. (default "/etc/kubernetes/admin.conf")
-      --rootfs string       [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init.md.orig

@@ -1,84 +0,0 @@
-
-Run this command in order to set up the Kubernetes control plane
-
-### Synopsis
-
-Run this command in order to set up the Kubernetes control plane
-
-The "init" command executes the following phases:
-```
-preflight                  Run pre-flight checks
-kubelet-start              Write kubelet settings and (re)start the kubelet
-certs                      Certificate generation
-  /etcd-ca                   Generate the self-signed CA to provision identities for etcd
-  /apiserver-etcd-client     Generate the certificate the apiserver uses to access etcd
-  /etcd-healthcheck-client   Generate the certificate for liveness probes to healtcheck etcd
-  /etcd-server               Generate the certificate for serving etcd
-  /etcd-peer                 Generate the certificate for etcd nodes to communicate with each other
-  /ca                        Generate the self-signed Kubernetes CA to provision identities for other Kubernetes components
-  /apiserver                 Generate the certificate for serving the Kubernetes API
-  /apiserver-kubelet-client  Generate the certificate for the API server to connect to kubelet
-  /front-proxy-ca            Generate the self-signed CA to provision identities for front proxy
-  /front-proxy-client        Generate the certificate for the front proxy client
-  /sa                        Generate a private key for signing service account tokens along with its public key
-kubeconfig                 Generate all kubeconfig files necessary to establish the control plane and the admin kubeconfig file
-  /admin                     Generate a kubeconfig file for the admin to use and for kubeadm itself
-  /kubelet                   Generate a kubeconfig file for the kubelet to use *only* for cluster bootstrapping purposes
-  /controller-manager        Generate a kubeconfig file for the controller manager to use
-  /scheduler                 Generate a kubeconfig file for the scheduler to use
-control-plane              Generate all static Pod manifest files necessary to establish the control plane
-  /apiserver                 Generates the kube-apiserver static Pod manifest
-  /controller-manager        Generates the kube-controller-manager static Pod manifest
-  /scheduler                 Generates the kube-scheduler static Pod manifest
-etcd                       Generate static Pod manifest file for local etcd
-  /local                     Generate the static Pod manifest file for a local, single-node local etcd instance
-upload-config              Upload the kubeadm and kubelet configuration to a ConfigMap
-  /kubeadm                   Upload the kubeadm ClusterConfiguration to a ConfigMap
-  /kubelet                   Upload the kubelet component config to a ConfigMap
-upload-certs               Upload certificates to kubeadm-certs
-mark-control-plane         Mark a node as a control-plane
-bootstrap-token            Generates bootstrap tokens used to join a node to a cluster
-addon                      Install required addons for passing Conformance tests
-  /coredns                   Install the CoreDNS addon to a Kubernetes cluster
-  /kube-proxy                Install the kube-proxy addon to a Kubernetes cluster
-```
-
-
-```
-kubeadm init [flags]
-```
-
-### Options
-
-```
-      --apiserver-advertise-address string   The IP address the API Server will advertise it's listening on. If not set the default network interface will be used.
-      --apiserver-bind-port int32            Port for the API Server to bind to. (default 6443)
-      --apiserver-cert-extra-sans strings    Optional extra Subject Alternative Names (SANs) to use for the API Server serving certificate. Can be both IP addresses and DNS names.
-      --cert-dir string                      The path where to save and store the certificates. (default "/etc/kubernetes/pki")
-      --certificate-key string               Key used to encrypt the control-plane certificates in the kubeadm-certs Secret.
-      --config string                        Path to a kubeadm configuration file.
-      --cri-socket string                    Path to the CRI socket to connect. If empty kubeadm will try to auto-detect this value; use this option only if you have more than one CRI installed or if you have non-standard CRI socket.
-      --dry-run                              Don't apply any changes; just output what would be done.
-      --feature-gates string                 A set of key=value pairs that describe feature gates for various features. No feature gates are available in this release.
-  -h, --help                                 help for init
-      --ignore-preflight-errors strings      A list of checks whose errors will be shown as warnings. Example: 'IsPrivilegedUser,Swap'. Value 'all' ignores errors from all checks.
-      --image-repository string              Choose a container registry to pull control plane images from (default "k8s.gcr.io")
-      --kubernetes-version string            Choose a specific Kubernetes version for the control plane. (default "stable-1")
-      --node-name string                     Specify the node name.
-      --pod-network-cidr string              Specify range of IP addresses for the pod network. If set, the control plane will automatically allocate CIDRs for every node.
-      --service-cidr string                  Use alternative range of IP address for service VIPs. (default "10.96.0.0/12")
-      --service-dns-domain string            Use alternative domain for services, e.g. "myorg.internal". (default "cluster.local")
-      --skip-certificate-key-print           Don't print the key used to encrypt the control-plane certificates.
-      --skip-phases strings                  List of phases to be skipped
-      --skip-token-print                     Skip printing of the default bootstrap token generated by 'kubeadm init'.
-      --token string                         The token to use for establishing bidirectional trust between nodes and control-plane nodes. The format is [a-z0-9]{6}\.[a-z0-9]{16} - e.g. abcdef.0123456789abcdef
-      --token-ttl duration                   The duration before the token is automatically deleted (e.g. 1s, 2m, 3h). If set to '0', the token will never expire (default 24h0m0s)
-      --upload-certs                         Upload control-plane certificates to the kubeadm-certs Secret.
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_addon_all.md.orig

@@ -1,33 +0,0 @@
-
-Install all the addons
-
-### Synopsis
-
-Install all the addons
-
-```
-kubeadm init phase addon all [flags]
-```
-
-### Options
-
-```
-      --apiserver-advertise-address string   The IP address the API Server will advertise it's listening on. If not set the default network interface will be used.
-      --apiserver-bind-port int32            Port for the API Server to bind to. (default 6443)
-      --config string                        Path to a kubeadm configuration file.
-      --feature-gates string                 A set of key=value pairs that describe feature gates for various features. No feature gates are available in this release.
-  -h, --help                                 help for all
-      --image-repository string              Choose a container registry to pull control plane images from (default "k8s.gcr.io")
-      --kubeconfig string                    The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. (default "/etc/kubernetes/admin.conf")
-      --kubernetes-version string            Choose a specific Kubernetes version for the control plane. (default "stable-1")
-      --pod-network-cidr string              Specify range of IP addresses for the pod network. If set, the control plane will automatically allocate CIDRs for every node.
-      --service-cidr string                  Use alternative range of IP address for service VIPs. (default "10.96.0.0/12")
-      --service-dns-domain string            Use alternative domain for services, e.g. "myorg.internal". (default "cluster.local")
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_addon_coredns.md.orig

@@ -1,30 +0,0 @@
-
-Install the CoreDNS addon to a Kubernetes cluster
-
-### Synopsis
-
-Install the CoreDNS addon components via the API server. Please note that although the DNS server is deployed, it will not be scheduled until CNI is installed.
-
-```
-kubeadm init phase addon coredns [flags]
-```
-
-### Options
-
-```
-      --config string               Path to a kubeadm configuration file.
-      --feature-gates string        A set of key=value pairs that describe feature gates for various features. No feature gates are available in this release.
-  -h, --help                        help for coredns
-      --image-repository string     Choose a container registry to pull control plane images from (default "k8s.gcr.io")
-      --kubeconfig string           The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. (default "/etc/kubernetes/admin.conf")
-      --kubernetes-version string   Choose a specific Kubernetes version for the control plane. (default "stable-1")
-      --service-cidr string         Use alternative range of IP address for service VIPs. (default "10.96.0.0/12")
-      --service-dns-domain string   Use alternative domain for services, e.g. "myorg.internal". (default "cluster.local")
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_addon_kube-proxy.md.orig

@@ -1,30 +0,0 @@
-
-Install the kube-proxy addon to a Kubernetes cluster
-
-### Synopsis
-
-Install the kube-proxy addon components via the API server.
-
-```
-kubeadm init phase addon kube-proxy [flags]
-```
-
-### Options
-
-```
-      --apiserver-advertise-address string   The IP address the API Server will advertise it's listening on. If not set the default network interface will be used.
-      --apiserver-bind-port int32            Port for the API Server to bind to. (default 6443)
-      --config string                        Path to a kubeadm configuration file.
-  -h, --help                                 help for kube-proxy
-      --image-repository string              Choose a container registry to pull control plane images from (default "k8s.gcr.io")
-      --kubeconfig string                    The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. (default "/etc/kubernetes/admin.conf")
-      --kubernetes-version string            Choose a specific Kubernetes version for the control plane. (default "stable-1")
-      --pod-network-cidr string              Specify range of IP addresses for the pod network. If set, the control plane will automatically allocate CIDRs for every node.
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_bootstrap-token.md.orig

@@ -1,36 +0,0 @@
-
-Generates bootstrap tokens used to join a node to a cluster
-
-### Synopsis
-
-Bootstrap tokens are used for establishing bidirectional trust between a node joining the cluster and a the control-plane node. 
-
-This command makes all the configurations required to make bootstrap tokens works and then creates an initial token.
-
-```
-kubeadm init phase bootstrap-token [flags]
-```
-
-### Examples
-
-```
-  # Make all the bootstrap token configurations and create an initial token, functionally
-  # equivalent to what generated by kubeadm init.
-  kubeadm init phase bootstrap-token
-```
-
-### Options
-
-```
-      --config string       Path to a kubeadm configuration file.
-  -h, --help                help for bootstrap-token
-      --kubeconfig string   The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. (default "/etc/kubernetes/admin.conf")
-      --skip-token-print    Skip printing of the default bootstrap token generated by 'kubeadm init'.
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_all.md.orig

@@ -1,29 +0,0 @@
-
-Generate all certificates
-
-### Synopsis
-
-Generate all certificates
-
-```
-kubeadm init phase certs all [flags]
-```
-
-### Options
-
-```
-      --apiserver-advertise-address string   The IP address the API Server will advertise it's listening on. If not set the default network interface will be used.
-      --apiserver-cert-extra-sans strings    Optional extra Subject Alternative Names (SANs) to use for the API Server serving certificate. Can be both IP addresses and DNS names.
-      --cert-dir string                      The path where to save and store the certificates. (default "/etc/kubernetes/pki")
-      --config string                        Path to a kubeadm configuration file.
-  -h, --help                                 help for all
-      --service-cidr string                  Use alternative range of IP address for service VIPs. (default "10.96.0.0/12")
-      --service-dns-domain string            Use alternative domain for services, e.g. "myorg.internal". (default "cluster.local")
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_apiserver-etcd-client.md.orig

@@ -1,31 +0,0 @@
-
-Generate the certificate the apiserver uses to access etcd
-
-### Synopsis
-
-Generate the certificate the apiserver uses to access etcd, and save them into apiserver-etcd-client.cert and apiserver-etcd-client.key files. 
-
-If both files already exist, kubeadm skips the generation step and existing files will be used. 
-
-Alpha Disclaimer: this command is currently alpha.
-
-```
-kubeadm init phase certs apiserver-etcd-client [flags]
-```
-
-### Options
-
-```
-      --cert-dir string   The path where to save and store the certificates. (default "/etc/kubernetes/pki")
-      --config string     Path to a kubeadm configuration file.
-      --csr-dir string    The path to output the CSRs and private keys to
-      --csr-only          Create CSRs instead of generating certificates
-  -h, --help              help for apiserver-etcd-client
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_apiserver-kubelet-client.md.orig

@@ -1,31 +0,0 @@
-
-Generate the certificate for the API server to connect to kubelet
-
-### Synopsis
-
-Generate the certificate for the API server to connect to kubelet, and save them into apiserver-kubelet-client.cert and apiserver-kubelet-client.key files. 
-
-If both files already exist, kubeadm skips the generation step and existing files will be used. 
-
-Alpha Disclaimer: this command is currently alpha.
-
-```
-kubeadm init phase certs apiserver-kubelet-client [flags]
-```
-
-### Options
-
-```
-      --cert-dir string   The path where to save and store the certificates. (default "/etc/kubernetes/pki")
-      --config string     Path to a kubeadm configuration file.
-      --csr-dir string    The path to output the CSRs and private keys to
-      --csr-only          Create CSRs instead of generating certificates
-  -h, --help              help for apiserver-kubelet-client
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_apiserver.md.orig

@@ -1,37 +0,0 @@
-
-Generate the certificate for serving the Kubernetes API
-
-### Synopsis
-
-Generate the certificate for serving the Kubernetes API, and save them into apiserver.cert and apiserver.key files.
-
-Default SANs are kubernetes, kubernetes.default, kubernetes.default.svc, kubernetes.default.svc.cluster.local, 10.96.0.1, 127.0.0.1 
-
-If both files already exist, kubeadm skips the generation step and existing files will be used. 
-
-Alpha Disclaimer: this command is currently alpha.
-
-```
-kubeadm init phase certs apiserver [flags]
-```
-
-### Options
-
-```
-      --apiserver-advertise-address string   The IP address the API Server will advertise it's listening on. If not set the default network interface will be used.
-      --apiserver-cert-extra-sans strings    Optional extra Subject Alternative Names (SANs) to use for the API Server serving certificate. Can be both IP addresses and DNS names.
-      --cert-dir string                      The path where to save and store the certificates. (default "/etc/kubernetes/pki")
-      --config string                        Path to a kubeadm configuration file.
-      --csr-dir string                       The path to output the CSRs and private keys to
-      --csr-only                             Create CSRs instead of generating certificates
-  -h, --help                                 help for apiserver
-      --service-cidr string                  Use alternative range of IP address for service VIPs. (default "10.96.0.0/12")
-      --service-dns-domain string            Use alternative domain for services, e.g. "myorg.internal". (default "cluster.local")
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_ca.md.orig

@@ -1,29 +0,0 @@
-
-Generate the self-signed Kubernetes CA to provision identities for other Kubernetes components
-
-### Synopsis
-
-Generate the self-signed Kubernetes CA to provision identities for other Kubernetes components, and save them into ca.cert and ca.key files. 
-
-If both files already exist, kubeadm skips the generation step and existing files will be used. 
-
-Alpha Disclaimer: this command is currently alpha.
-
-```
-kubeadm init phase certs ca [flags]
-```
-
-### Options
-
-```
-      --cert-dir string   The path where to save and store the certificates. (default "/etc/kubernetes/pki")
-      --config string     Path to a kubeadm configuration file.
-  -h, --help              help for ca
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_etcd-ca.md.orig

@@ -1,29 +0,0 @@
-
-Generate the self-signed CA to provision identities for etcd
-
-### Synopsis
-
-Generate the self-signed CA to provision identities for etcd, and save them into etcd/ca.cert and etcd/ca.key files. 
-
-If both files already exist, kubeadm skips the generation step and existing files will be used. 
-
-Alpha Disclaimer: this command is currently alpha.
-
-```
-kubeadm init phase certs etcd-ca [flags]
-```
-
-### Options
-
-```
-      --cert-dir string   The path where to save and store the certificates. (default "/etc/kubernetes/pki")
-      --config string     Path to a kubeadm configuration file.
-  -h, --help              help for etcd-ca
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_etcd-healthcheck-client.md.orig

@@ -1,31 +0,0 @@
-
-Generate the certificate for liveness probes to healtcheck etcd
-
-### Synopsis
-
-Generate the certificate for liveness probes to healtcheck etcd, and save them into etcd/healthcheck-client.cert and etcd/healthcheck-client.key files. 
-
-If both files already exist, kubeadm skips the generation step and existing files will be used. 
-
-Alpha Disclaimer: this command is currently alpha.
-
-```
-kubeadm init phase certs etcd-healthcheck-client [flags]
-```
-
-### Options
-
-```
-      --cert-dir string   The path where to save and store the certificates. (default "/etc/kubernetes/pki")
-      --config string     Path to a kubeadm configuration file.
-      --csr-dir string    The path to output the CSRs and private keys to
-      --csr-only          Create CSRs instead of generating certificates
-  -h, --help              help for etcd-healthcheck-client
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_etcd-peer.md.orig

@@ -1,33 +0,0 @@
-
-Generate the certificate for etcd nodes to communicate with each other
-
-### Synopsis
-
-Generate the certificate for etcd nodes to communicate with each other, and save them into etcd/peer.cert and etcd/peer.key files.
-
-Default SANs are localhost, 127.0.0.1, 127.0.0.1, ::1 
-
-If both files already exist, kubeadm skips the generation step and existing files will be used. 
-
-Alpha Disclaimer: this command is currently alpha.
-
-```
-kubeadm init phase certs etcd-peer [flags]
-```
-
-### Options
-
-```
-      --cert-dir string   The path where to save and store the certificates. (default "/etc/kubernetes/pki")
-      --config string     Path to a kubeadm configuration file.
-      --csr-dir string    The path to output the CSRs and private keys to
-      --csr-only          Create CSRs instead of generating certificates
-  -h, --help              help for etcd-peer
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_etcd-server.md.orig

@@ -1,33 +0,0 @@
-
-Generate the certificate for serving etcd
-
-### Synopsis
-
-Generate the certificate for serving etcd, and save them into etcd/server.cert and etcd/server.key files.
-
-Default SANs are localhost, 127.0.0.1, 127.0.0.1, ::1 
-
-If both files already exist, kubeadm skips the generation step and existing files will be used. 
-
-Alpha Disclaimer: this command is currently alpha.
-
-```
-kubeadm init phase certs etcd-server [flags]
-```
-
-### Options
-
-```
-      --cert-dir string   The path where to save and store the certificates. (default "/etc/kubernetes/pki")
-      --config string     Path to a kubeadm configuration file.
-      --csr-dir string    The path to output the CSRs and private keys to
-      --csr-only          Create CSRs instead of generating certificates
-  -h, --help              help for etcd-server
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_front-proxy-ca.md.orig

@@ -1,29 +0,0 @@
-
-Generate the self-signed CA to provision identities for front proxy
-
-### Synopsis
-
-Generate the self-signed CA to provision identities for front proxy, and save them into front-proxy-ca.cert and front-proxy-ca.key files. 
-
-If both files already exist, kubeadm skips the generation step and existing files will be used. 
-
-Alpha Disclaimer: this command is currently alpha.
-
-```
-kubeadm init phase certs front-proxy-ca [flags]
-```
-
-### Options
-
-```
-      --cert-dir string   The path where to save and store the certificates. (default "/etc/kubernetes/pki")
-      --config string     Path to a kubeadm configuration file.
-  -h, --help              help for front-proxy-ca
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_front-proxy-client.md.orig

@@ -1,31 +0,0 @@
-
-Generate the certificate for the front proxy client
-
-### Synopsis
-
-Generate the certificate for the front proxy client, and save them into front-proxy-client.cert and front-proxy-client.key files. 
-
-If both files already exist, kubeadm skips the generation step and existing files will be used. 
-
-Alpha Disclaimer: this command is currently alpha.
-
-```
-kubeadm init phase certs front-proxy-client [flags]
-```
-
-### Options
-
-```
-      --cert-dir string   The path where to save and store the certificates. (default "/etc/kubernetes/pki")
-      --config string     Path to a kubeadm configuration file.
-      --csr-dir string    The path to output the CSRs and private keys to
-      --csr-only          Create CSRs instead of generating certificates
-  -h, --help              help for front-proxy-client
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_sa.md.orig

@@ -1,26 +0,0 @@
-
-Generate a private key for signing service account tokens along with its public key
-
-### Synopsis
-
-Generate the private key for signing service account tokens along with its public key, and save them into sa.key and sa.pub files. If both files already exist, kubeadm skips the generation step and existing files will be used. 
-
-Alpha Disclaimer: this command is currently alpha.
-
-```
-kubeadm init phase certs sa [flags]
-```
-
-### Options
-
-```
-      --cert-dir string   The path where to save and store the certificates. (default "/etc/kubernetes/pki")
-  -h, --help              help for sa
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_control-plane_all.md.orig

@@ -1,46 +0,0 @@
-
-Generate all static Pod manifest files
-
-### Synopsis
-
-Generate all static Pod manifest files
-
-```
-kubeadm init phase control-plane all [flags]
-```
-
-### Examples
-
-```
-  # Generates all static Pod manifest files for control plane components,
-  # functionally equivalent to what is generated by kubeadm init.
-  kubeadm init phase control-plane all
-  
-  # Generates all static Pod manifest files using options read from a configuration file.
-  kubeadm init phase control-plane all --config config.yaml
-```
-
-### Options
-
-```
-      --apiserver-advertise-address string              The IP address the API Server will advertise it's listening on. If not set the default network interface will be used.
-      --apiserver-bind-port int32                       Port for the API Server to bind to. (default 6443)
-      --apiserver-extra-args mapStringString            A set of extra flags to pass to the API Server or override default ones in form of <flagname>=<value>
-      --cert-dir string                                 The path where to save and store the certificates. (default "/etc/kubernetes/pki")
-      --config string                                   Path to a kubeadm configuration file.
-      --controller-manager-extra-args mapStringString   A set of extra flags to pass to the Controller Manager or override default ones in form of <flagname>=<value>
-      --feature-gates string                            A set of key=value pairs that describe feature gates for various features. No feature gates are available in this release.
-  -h, --help                                            help for all
-      --image-repository string                         Choose a container registry to pull control plane images from (default "k8s.gcr.io")
-      --kubernetes-version string                       Choose a specific Kubernetes version for the control plane. (default "stable-1")
-      --pod-network-cidr string                         Specify range of IP addresses for the pod network. If set, the control plane will automatically allocate CIDRs for every node.
-      --scheduler-extra-args mapStringString            A set of extra flags to pass to the Scheduler or override default ones in form of <flagname>=<value>
-      --service-cidr string                             Use alternative range of IP address for service VIPs. (default "10.96.0.0/12")
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_control-plane_apiserver.md.orig

@@ -1,32 +0,0 @@
-
-Generates the kube-apiserver static Pod manifest
-
-### Synopsis
-
-Generates the kube-apiserver static Pod manifest
-
-```
-kubeadm init phase control-plane apiserver [flags]
-```
-
-### Options
-
-```
-      --apiserver-advertise-address string     The IP address the API Server will advertise it's listening on. If not set the default network interface will be used.
-      --apiserver-bind-port int32              Port for the API Server to bind to. (default 6443)
-      --apiserver-extra-args mapStringString   A set of extra flags to pass to the API Server or override default ones in form of <flagname>=<value>
-      --cert-dir string                        The path where to save and store the certificates. (default "/etc/kubernetes/pki")
-      --config string                          Path to a kubeadm configuration file.
-      --feature-gates string                   A set of key=value pairs that describe feature gates for various features. No feature gates are available in this release.
-  -h, --help                                   help for apiserver
-      --image-repository string                Choose a container registry to pull control plane images from (default "k8s.gcr.io")
-      --kubernetes-version string              Choose a specific Kubernetes version for the control plane. (default "stable-1")
-      --service-cidr string                    Use alternative range of IP address for service VIPs. (default "10.96.0.0/12")
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_control-plane_controller-manager.md.orig

@@ -1,29 +0,0 @@
-
-Generates the kube-controller-manager static Pod manifest
-
-### Synopsis
-
-Generates the kube-controller-manager static Pod manifest
-
-```
-kubeadm init phase control-plane controller-manager [flags]
-```
-
-### Options
-
-```
-      --cert-dir string                                 The path where to save and store the certificates. (default "/etc/kubernetes/pki")
-      --config string                                   Path to a kubeadm configuration file.
-      --controller-manager-extra-args mapStringString   A set of extra flags to pass to the Controller Manager or override default ones in form of <flagname>=<value>
-  -h, --help                                            help for controller-manager
-      --image-repository string                         Choose a container registry to pull control plane images from (default "k8s.gcr.io")
-      --kubernetes-version string                       Choose a specific Kubernetes version for the control plane. (default "stable-1")
-      --pod-network-cidr string                         Specify range of IP addresses for the pod network. If set, the control plane will automatically allocate CIDRs for every node.
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_control-plane_scheduler.md.orig

@@ -1,28 +0,0 @@
-
-Generates the kube-scheduler static Pod manifest
-
-### Synopsis
-
-Generates the kube-scheduler static Pod manifest
-
-```
-kubeadm init phase control-plane scheduler [flags]
-```
-
-### Options
-
-```
-      --cert-dir string                        The path where to save and store the certificates. (default "/etc/kubernetes/pki")
-      --config string                          Path to a kubeadm configuration file.
-  -h, --help                                   help for scheduler
-      --image-repository string                Choose a container registry to pull control plane images from (default "k8s.gcr.io")
-      --kubernetes-version string              Choose a specific Kubernetes version for the control plane. (default "stable-1")
-      --scheduler-extra-args mapStringString   A set of extra flags to pass to the Scheduler or override default ones in form of <flagname>=<value>
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_etcd_local.md.orig

@@ -1,38 +0,0 @@
-
-Generate the static Pod manifest file for a local, single-node local etcd instance
-
-### 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
-
-```
-      --cert-dir string           The path where to save and store the certificates. (default "/etc/kubernetes/pki")
-      --config string             Path to a kubeadm configuration file.
-  -h, --help                      help for local
-      --image-repository string   Choose a container registry to pull control plane images from (default "k8s.gcr.io")
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_kubeconfig_admin.md.orig

@@ -1,28 +0,0 @@
-
-Generate a kubeconfig file for the admin to use and for kubeadm itself
-
-### Synopsis
-
-Generate the kubeconfig file for the admin and for kubeadm itself, and save it to admin.conf file.
-
-```
-kubeadm init phase kubeconfig admin [flags]
-```
-
-### Options
-
-```
-      --apiserver-advertise-address string   The IP address the API Server will advertise it's listening on. If not set the default network interface will be used.
-      --apiserver-bind-port int32            Port for the API Server to bind to. (default 6443)
-      --cert-dir string                      The path where to save and store the certificates. (default "/etc/kubernetes/pki")
-      --config string                        Path to a kubeadm configuration file.
-  -h, --help                                 help for admin
-      --kubeconfig-dir string                The path where to save the kubeconfig file. (default "/etc/kubernetes")
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_kubeconfig_all.md.orig

@@ -1,29 +0,0 @@
-
-Generate all kubeconfig files
-
-### Synopsis
-
-Generate all kubeconfig files
-
-```
-kubeadm init phase kubeconfig all [flags]
-```
-
-### Options
-
-```
-      --apiserver-advertise-address string   The IP address the API Server will advertise it's listening on. If not set the default network interface will be used.
-      --apiserver-bind-port int32            Port for the API Server to bind to. (default 6443)
-      --cert-dir string                      The path where to save and store the certificates. (default "/etc/kubernetes/pki")
-      --config string                        Path to a kubeadm configuration file.
-  -h, --help                                 help for all
-      --kubeconfig-dir string                The path where to save the kubeconfig file. (default "/etc/kubernetes")
-      --node-name string                     Specify the node name.
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_kubeconfig_controller-manager.md.orig

@@ -1,28 +0,0 @@
-
-Generate a kubeconfig file for the controller manager to use
-
-### Synopsis
-
-Generate the kubeconfig file for the controller manager to use and save it to controller-manager.conf file
-
-```
-kubeadm init phase kubeconfig controller-manager [flags]
-```
-
-### Options
-
-```
-      --apiserver-advertise-address string   The IP address the API Server will advertise it's listening on. If not set the default network interface will be used.
-      --apiserver-bind-port int32            Port for the API Server to bind to. (default 6443)
-      --cert-dir string                      The path where to save and store the certificates. (default "/etc/kubernetes/pki")
-      --config string                        Path to a kubeadm configuration file.
-  -h, --help                                 help for controller-manager
-      --kubeconfig-dir string                The path where to save the kubeconfig file. (default "/etc/kubernetes")
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_kubeconfig_kubelet.md.orig

@@ -1,31 +0,0 @@
-
-Generate a kubeconfig file for the kubelet to use *only* for cluster bootstrapping purposes
-
-### Synopsis
-
-Generate the kubeconfig file for the kubelet to use and save it to kubelet.conf file. 
-
-Please note that this should only be used for cluster bootstrapping purposes. After your control plane is up, you should request all kubelet credentials from the CSR API.
-
-```
-kubeadm init phase kubeconfig kubelet [flags]
-```
-
-### Options
-
-```
-      --apiserver-advertise-address string   The IP address the API Server will advertise it's listening on. If not set the default network interface will be used.
-      --apiserver-bind-port int32            Port for the API Server to bind to. (default 6443)
-      --cert-dir string                      The path where to save and store the certificates. (default "/etc/kubernetes/pki")
-      --config string                        Path to a kubeadm configuration file.
-  -h, --help                                 help for kubelet
-      --kubeconfig-dir string                The path where to save the kubeconfig file. (default "/etc/kubernetes")
-      --node-name string                     Specify the node name.
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_kubeconfig_scheduler.md.orig

@@ -1,28 +0,0 @@
-
-Generate a kubeconfig file for the scheduler to use
-
-### Synopsis
-
-Generate the kubeconfig file for the scheduler to use and save it to scheduler.conf file.
-
-```
-kubeadm init phase kubeconfig scheduler [flags]
-```
-
-### Options
-
-```
-      --apiserver-advertise-address string   The IP address the API Server will advertise it's listening on. If not set the default network interface will be used.
-      --apiserver-bind-port int32            Port for the API Server to bind to. (default 6443)
-      --cert-dir string                      The path where to save and store the certificates. (default "/etc/kubernetes/pki")
-      --config string                        Path to a kubeadm configuration file.
-  -h, --help                                 help for scheduler
-      --kubeconfig-dir string                The path where to save the kubeconfig file. (default "/etc/kubernetes")
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_kubelet-start.md.orig

@@ -1,33 +0,0 @@
-
-Write kubelet settings and (re)start the kubelet
-
-### Synopsis
-
-Write a file with KubeletConfiguration and an environment file with node specific kubelet settings, and then (re)start kubelet.
-
-```
-kubeadm init phase kubelet-start [flags]
-```
-
-### Examples
-
-```
-  # Writes a dynamic environment file with kubelet flags from a InitConfiguration file.
-  kubeadm init phase kubelet-start --config config.yaml
-```
-
-### Options
-
-```
-      --config string       Path to a kubeadm configuration file.
-      --cri-socket string   Path to the CRI socket to connect. If empty kubeadm will try to auto-detect this value; use this option only if you have more than one CRI installed or if you have non-standard CRI socket.
-  -h, --help                help for kubelet-start
-      --node-name string    Specify the node name.
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_mark-control-plane.md.orig

@@ -1,35 +0,0 @@
-
-Mark a node as a control-plane
-
-### Synopsis
-
-Mark a node as a control-plane
-
-```
-kubeadm init phase mark-control-plane [flags]
-```
-
-### Examples
-
-```
-  # Applies control-plane label and taint to the current node, functionally equivalent to what executed by kubeadm init.
-  kubeadm init phase mark-control-plane --config config.yml
-  
-  # Applies control-plane label and taint to a specific node
-  kubeadm init phase mark-control-plane --node-name myNode
-```
-
-### Options
-
-```
-      --config string      Path to a kubeadm configuration file.
-  -h, --help               help for mark-control-plane
-      --node-name string   Specify the node name.
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_preflight.md.orig

@@ -1,32 +0,0 @@
-
-Run pre-flight checks
-
-### Synopsis
-
-Run pre-flight checks for kubeadm init.
-
-```
-kubeadm init phase preflight [flags]
-```
-
-### Examples
-
-```
-  # Run pre-flight checks for kubeadm init using a config file.
-  kubeadm init phase preflight --config kubeadm-config.yml
-```
-
-### Options
-
-```
-      --config string                     Path to a kubeadm configuration file.
-  -h, --help                              help for preflight
-      --ignore-preflight-errors strings   A list of checks whose errors will be shown as warnings. Example: 'IsPrivilegedUser,Swap'. Value 'all' ignores errors from all checks.
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_upload-certs.md.orig

@@ -1,43 +0,0 @@
-
-Upload certificates to kubeadm-certs
-
-### Synopsis
-
-
-This command is not meant to be run on its own. See list of available subcommands.
-
-```
-kubeadm init phase upload-certs [flags]
-```
-
-### Options
-
-```
-      --certificate-key string       Key used to encrypt the control-plane certificates in the kubeadm-certs Secret.
-      --config string                Path to a kubeadm configuration file.
-  -h, --help                         help for upload-certs
-      --skip-certificate-key-print   Don't print the key used to encrypt the control-plane certificates.
-      --upload-certs                 Upload control-plane certificates to the kubeadm-certs Secret.
-```
-
-### 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;">[EXPERIMENTAL] The path to the 'real' host root filesystem.</td>
-    </tr>
-
-  </tbody>
-</table>
-
-
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_upload-config_all.md.orig

@@ -1,25 +0,0 @@
-
-Upload all configuration to a config map
-
-### Synopsis
-
-Upload all configuration to a config map
-
-```
-kubeadm init phase upload-config all [flags]
-```
-
-### Options
-
-```
-      --config string       Path to a kubeadm configuration file.
-  -h, --help                help for all
-      --kubeconfig string   The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. (default "/etc/kubernetes/admin.conf")
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_upload-config_kubeadm.md.orig

@@ -1,34 +0,0 @@
-
-Upload the kubeadm ClusterConfiguration to a ConfigMap
-
-### Synopsis
-
-Upload the kubeadm ClusterConfiguration to a ConfigMap called kubeadm-config in the kube-system namespace. This enables correct configuration of system components and a seamless user experience when upgrading. 
-
-Alternatively, you can use kubeadm config.
-
-```
-kubeadm init phase upload-config kubeadm [flags]
-```
-
-### Examples
-
-```
-  # upload the configuration of your cluster
-  kubeadm init phase upload-config --config=myConfig.yaml
-```
-
-### Options
-
-```
-      --config string       Path to a kubeadm configuration file.
-  -h, --help                help for kubeadm
-      --kubeconfig string   The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. (default "/etc/kubernetes/admin.conf")
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_upload-config_kubelet.md.orig

@@ -1,32 +0,0 @@
-
-Upload the kubelet component config to a ConfigMap
-
-### Synopsis
-
-Upload kubelet configuration extracted from the kubeadm InitConfiguration object to a ConfigMap of the form kubelet-config-1.X in the cluster, where X is the minor version of the current (API Server) Kubernetes version.
-
-```
-kubeadm init phase upload-config kubelet [flags]
-```
-
-### Examples
-
-```
-  # Upload the kubelet configuration from the kubeadm Config file to a ConfigMap in the cluster.
-  kubeadm init phase upload-config kubelet --config kubeadm.yaml
-```
-
-### Options
-
-```
-      --config string       Path to a kubeadm configuration file.
-  -h, --help                help for kubelet
-      --kubeconfig string   The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. (default "/etc/kubernetes/admin.conf")
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_join.md.orig

@@ -1,96 +0,0 @@
-
-Run this on any machine you wish to join an existing cluster
-
-### Synopsis
-
-
-When joining a kubeadm initialized cluster, we need to establish
-bidirectional trust. This is split into discovery (having the Node
-trust the Kubernetes Control Plane) and TLS bootstrap (having the
-Kubernetes Control Plane trust the Node).
-
-There are 2 main schemes for discovery. The first is to use a shared
-token along with the IP address of the API server. The second is to
-provide a file - a subset of the standard kubeconfig file. This file
-can be a local file or downloaded via an HTTPS URL. The forms are
-kubeadm join --discovery-token abcdef.1234567890abcdef 1.2.3.4:6443,
-kubeadm join --discovery-file path/to/file.conf, or kubeadm join
---discovery-file https://url/file.conf. Only one form can be used. If
-the discovery information is loaded from a URL, HTTPS must be used.
-Also, in that case the host installed CA bundle is used to verify
-the connection.
-
-If you use a shared token for discovery, you should also pass the
---discovery-token-ca-cert-hash flag to validate the public key of the
-root certificate authority (CA) presented by the Kubernetes Control Plane.
-The value of this flag is specified as "<hash-type>:<hex-encoded-value>",
-where the supported hash type is "sha256". The hash is calculated over
-the bytes of the Subject Public Key Info (SPKI) object (as in RFC7469).
-This value is available in the output of "kubeadm init" or can be
-calculated using standard tools. The --discovery-token-ca-cert-hash flag
-may be repeated multiple times to allow more than one public key.
-
-If you cannot know the CA public key hash ahead of time, you can pass
-the --discovery-token-unsafe-skip-ca-verification flag to disable this
-verification. This weakens the kubeadm security model since other nodes
-can potentially impersonate the Kubernetes Control Plane.
-
-The TLS bootstrap mechanism is also driven via a shared token. This is
-used to temporarily authenticate with the Kubernetes Control Plane to submit a
-certificate signing request (CSR) for a locally created key pair. By
-default, kubeadm will set up the Kubernetes Control Plane to automatically
-approve these signing requests. This token is passed in with the
---tls-bootstrap-token abcdef.1234567890abcdef flag.
-
-Often times the same token is used for both parts. In this case, the
---token flag can be used instead of specifying each token individually.
-
-
-The "join [api-server-endpoint]" command executes the following phases:
-```
-preflight              Run join pre-flight checks
-control-plane-prepare  Prepare the machine for serving a control plane
-  /download-certs        [EXPERIMENTAL] Download certificates shared among control-plane nodes from the kubeadm-certs Secret
-  /certs                 Generate the certificates for the new control plane components
-  /kubeconfig            Generate the kubeconfig for the new control plane components
-  /control-plane         Generate the manifests for the new control plane components
-kubelet-start          Write kubelet settings, certificates and (re)start the kubelet
-control-plane-join     Join a machine as a control plane instance
-  /etcd                  Add a new local etcd member
-  /update-status         Register the new control-plane node into the ClusterStatus maintained in the kubeadm-config ConfigMap
-  /mark-control-plane    Mark a node as a control-plane
-```
-
-
-```
-kubeadm join [api-server-endpoint] [flags]
-```
-
-### Options
-
-```
-      --apiserver-advertise-address string            If the node should host a new control plane instance, the IP address the API Server will advertise it's listening on. If not set the default network interface will be used.
-      --apiserver-bind-port int32                     If the node should host a new control plane instance, the port for the API Server to bind to. (default 6443)
-      --certificate-key string                        Use this key to decrypt the certificate secrets uploaded by init.
-      --config string                                 Path to kubeadm config file.
-      --control-plane                                 Create a new control plane instance on this node
-      --cri-socket string                             Path to the CRI socket to connect. If empty kubeadm will try to auto-detect this value; use this option only if you have more than one CRI installed or if you have non-standard CRI socket.
-      --discovery-file string                         For file-based discovery, a file or URL from which to load cluster information.
-      --discovery-token string                        For token-based discovery, the token used to validate cluster information fetched from the API server.
-      --discovery-token-ca-cert-hash strings          For token-based discovery, validate that the root CA public key matches this hash (format: "<type>:<value>").
-      --discovery-token-unsafe-skip-ca-verification   For token-based discovery, allow joining without --discovery-token-ca-cert-hash pinning.
-      --experimental-control-plane                    Create a new control plane instance on this node
-  -h, --help                                          help for join
-      --ignore-preflight-errors strings               A list of checks whose errors will be shown as warnings. Example: 'IsPrivilegedUser,Swap'. Value 'all' ignores errors from all checks.
-      --node-name string                              Specify the node name.
-      --skip-phases strings                           List of phases to be skipped
-      --tls-bootstrap-token string                    Specify the token used to temporarily authenticate with the Kubernetes Control Plane while joining the node.
-      --token string                                  Use this token for both discovery-token and tls-bootstrap-token when those values are not provided.
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase.md.orig

@@ -1,49 +0,0 @@
-
-Use this command to invoke single phase of the join workflow
-
-### Synopsis
-
-Use this command to invoke single phase of the join workflow
-
-### Options
-
-<table style="width: 100%; table-layout: fixed;">
-  <colgroup>
-    <col span="1" style="width: 10px;" />
-    <col span="1" />
-  </colgroup>
-  <tbody>
-
-    <tr>
-      <td colspan="2">-h, --help</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">help for phase</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;">[EXPERIMENTAL] The path to the 'real' host root filesystem.</td>
-    </tr>
-
-  </tbody>
-</table>
-
-
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_control-plane-join.md.orig

@@ -1,60 +0,0 @@
-
-Join a machine as a control plane instance
-
-### Synopsis
-
-Join a machine as a control plane instance
-
-```
-kubeadm join phase control-plane-join [flags]
-```
-
-### Examples
-
-```
-  # Joins a machine as a control plane instance
-  kubeadm join phase control-plane-join all
-```
-
-### Options
-
-<table style="width: 100%; table-layout: fixed;">
-  <colgroup>
-    <col span="1" style="width: 10px;" />
-    <col span="1" />
-  </colgroup>
-  <tbody>
-
-    <tr>
-      <td colspan="2">-h, --help</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">help for control-plane-join</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;">[EXPERIMENTAL] The path to the 'real' host root filesystem.</td>
-    </tr>
-
-  </tbody>
-</table>
-
-
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_control-plane-join_all.md.orig

@@ -1,43 +0,0 @@
-
-Join a machine as a control plane instance
-
-### Synopsis
-
-Join a machine as a control plane instance
-
-```
-kubeadm join phase control-plane-join all [flags]
-```
-
-### Options
-
-```
-      --apiserver-advertise-address string   If the node should host a new control plane instance, the IP address the API Server will advertise it's listening on. If not set the default network interface will be used.
-      --config string                        Path to kubeadm config file.
-      --control-plane                        Create a new control plane instance on this node
-      --experimental-control-plane           Create a new control plane instance on this node
-  -h, --help                                 help for all
-      --node-name string                     Specify the node name.
-```
-
-### 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;">[EXPERIMENTAL] The path to the 'real' host root filesystem.</td>
-    </tr>
-
-  </tbody>
-</table>
-
-
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_control-plane-join_etcd.md.orig

@@ -1,44 +0,0 @@
-
-Add a new local etcd member
-
-### Synopsis
-
-
-Add a new local etcd member
-
-```
-kubeadm join phase control-plane-join etcd [flags]
-```
-
-### Options
-
-```
-      --apiserver-advertise-address string   If the node should host a new control plane instance, the IP address the API Server will advertise it's listening on. If not set the default network interface will be used.
-      --config string                        Path to kubeadm config file.
-      --control-plane                        Create a new control plane instance on this node
-      --experimental-control-plane           Create a new control plane instance on this node
-  -h, --help                                 help for etcd
-      --node-name string                     Specify the node name.
-```
-
-### 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;">[EXPERIMENTAL] The path to the 'real' host root filesystem.</td>
-    </tr>
-
-  </tbody>
-</table>
-
-
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_control-plane-join_mark-control-plane.md.orig

@@ -1,43 +0,0 @@
-
-Mark a node as a control-plane
-
-### Synopsis
-
-
-Mark a node as a control-plane
-
-```
-kubeadm join phase control-plane-join mark-control-plane [flags]
-```
-
-### Options
-
-```
-      --config string                Path to kubeadm config file.
-      --control-plane                Create a new control plane instance on this node
-      --experimental-control-plane   Create a new control plane instance on this node
-  -h, --help                         help for mark-control-plane
-      --node-name string             Specify the node name.
-```
-
-### 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;">[EXPERIMENTAL] The path to the 'real' host root filesystem.</td>
-    </tr>
-
-  </tbody>
-</table>
-
-
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_control-plane-join_update-status.md.orig

@@ -1,44 +0,0 @@
-
-Register the new control-plane node into the ClusterStatus maintained in the kubeadm-config ConfigMap
-
-### Synopsis
-
-
-Register the new control-plane node into the ClusterStatus maintained in the kubeadm-config ConfigMap
-
-```
-kubeadm join phase control-plane-join update-status [flags]
-```
-
-### Options
-
-```
-      --apiserver-advertise-address string   If the node should host a new control plane instance, the IP address the API Server will advertise it's listening on. If not set the default network interface will be used.
-      --config string                        Path to kubeadm config file.
-      --control-plane                        Create a new control plane instance on this node
-      --experimental-control-plane           Create a new control plane instance on this node
-  -h, --help                                 help for update-status
-      --node-name string                     Specify the node name.
-```
-
-### 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;">[EXPERIMENTAL] The path to the 'real' host root filesystem.</td>
-    </tr>
-
-  </tbody>
-</table>
-
-
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_control-plane-prepare.md.orig

@@ -1,60 +0,0 @@
-
-Prepare the machine for serving a control plane
-
-### Synopsis
-
-Prepare the machine for serving a control plane
-
-```
-kubeadm join phase control-plane-prepare [flags]
-```
-
-### Examples
-
-```
-  # Prepares the machine for serving a control plane
-  kubeadm join phase control-plane-prepare all
-```
-
-### Options
-
-<table style="width: 100%; table-layout: fixed;">
-  <colgroup>
-    <col span="1" style="width: 10px;" />
-    <col span="1" />
-  </colgroup>
-  <tbody>
-
-    <tr>
-      <td colspan="2">-h, --help</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">help for control-plane-prepare</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;">[EXPERIMENTAL] The path to the 'real' host root filesystem.</td>
-    </tr>
-
-  </tbody>
-</table>
-
-
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_control-plane-prepare_all.md.orig

@@ -1,51 +0,0 @@
-
-Prepare the machine for serving a control plane
-
-### Synopsis
-
-Prepare the machine for serving a control plane
-
-```
-kubeadm join phase control-plane-prepare all [api-server-endpoint] [flags]
-```
-
-### Options
-
-```
-      --apiserver-advertise-address string            If the node should host a new control plane instance, the IP address the API Server will advertise it's listening on. If not set the default network interface will be used.
-      --apiserver-bind-port int32                     If the node should host a new control plane instance, the port for the API Server to bind to. (default 6443)
-      --certificate-key string                        Use this key to decrypt the certificate secrets uploaded by init.
-      --config string                                 Path to kubeadm config file.
-      --control-plane                                 Create a new control plane instance on this node
-      --discovery-file string                         For file-based discovery, a file or URL from which to load cluster information.
-      --discovery-token string                        For token-based discovery, the token used to validate cluster information fetched from the API server.
-      --discovery-token-ca-cert-hash strings          For token-based discovery, validate that the root CA public key matches this hash (format: "<type>:<value>").
-      --discovery-token-unsafe-skip-ca-verification   For token-based discovery, allow joining without --discovery-token-ca-cert-hash pinning.
-      --experimental-control-plane                    Create a new control plane instance on this node
-  -h, --help                                          help for all
-      --node-name string                              Specify the node name.
-      --tls-bootstrap-token string                    Specify the token used to temporarily authenticate with the Kubernetes Control Plane while joining the node.
-      --token string                                  Use this token for both discovery-token and tls-bootstrap-token when those values are not provided.
-```
-
-### 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;">[EXPERIMENTAL] The path to the 'real' host root filesystem.</td>
-    </tr>
-
-  </tbody>
-</table>
-
-
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_control-plane-prepare_certs.md.orig

@@ -1,49 +0,0 @@
-
-Generate the certificates for the new control plane components
-
-### Synopsis
-
-Generate the certificates for the new control plane components
-
-```
-kubeadm join phase control-plane-prepare certs [api-server-endpoint] [flags]
-```
-
-### Options
-
-```
-      --apiserver-advertise-address string            If the node should host a new control plane instance, the IP address the API Server will advertise it's listening on. If not set the default network interface will be used.
-      --config string                                 Path to kubeadm config file.
-      --control-plane                                 Create a new control plane instance on this node
-      --discovery-file string                         For file-based discovery, a file or URL from which to load cluster information.
-      --discovery-token string                        For token-based discovery, the token used to validate cluster information fetched from the API server.
-      --discovery-token-ca-cert-hash strings          For token-based discovery, validate that the root CA public key matches this hash (format: "<type>:<value>").
-      --discovery-token-unsafe-skip-ca-verification   For token-based discovery, allow joining without --discovery-token-ca-cert-hash pinning.
-      --experimental-control-plane                    Create a new control plane instance on this node
-  -h, --help                                          help for certs
-      --node-name string                              Specify the node name.
-      --tls-bootstrap-token string                    Specify the token used to temporarily authenticate with the Kubernetes Control Plane while joining the node.
-      --token string                                  Use this token for both discovery-token and tls-bootstrap-token when those values are not provided.
-```
-
-### 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;">[EXPERIMENTAL] The path to the 'real' host root filesystem.</td>
-    </tr>
-
-  </tbody>
-</table>
-
-
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_control-plane-prepare_control-plane.md.orig

@@ -1,43 +0,0 @@
-
-Generate the manifests for the new control plane components
-
-### Synopsis
-
-Generate the manifests for the new control plane components
-
-```
-kubeadm join phase control-plane-prepare control-plane [flags]
-```
-
-### Options
-
-```
-      --apiserver-advertise-address string   If the node should host a new control plane instance, the IP address the API Server will advertise it's listening on. If not set the default network interface will be used.
-      --apiserver-bind-port int32            If the node should host a new control plane instance, the port for the API Server to bind to. (default 6443)
-      --config string                        Path to kubeadm config file.
-      --control-plane                        Create a new control plane instance on this node
-      --experimental-control-plane           Create a new control plane instance on this node
-  -h, --help                                 help for control-plane
-```
-
-### 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;">[EXPERIMENTAL] The path to the 'real' host root filesystem.</td>
-    </tr>
-
-  </tbody>
-</table>
-
-
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_control-plane-prepare_download-certs.md.orig

@@ -1,48 +0,0 @@
-
-[EXPERIMENTAL] Download certificates shared among control-plane nodes from the kubeadm-certs Secret
-
-### Synopsis
-
-[EXPERIMENTAL] Download certificates shared among control-plane nodes from the kubeadm-certs Secret
-
-```
-kubeadm join phase control-plane-prepare download-certs [api-server-endpoint] [flags]
-```
-
-### Options
-
-```
-      --certificate-key string                        Use this key to decrypt the certificate secrets uploaded by init.
-      --config string                                 Path to kubeadm config file.
-      --control-plane                                 Create a new control plane instance on this node
-      --discovery-file string                         For file-based discovery, a file or URL from which to load cluster information.
-      --discovery-token string                        For token-based discovery, the token used to validate cluster information fetched from the API server.
-      --discovery-token-ca-cert-hash strings          For token-based discovery, validate that the root CA public key matches this hash (format: "<type>:<value>").
-      --discovery-token-unsafe-skip-ca-verification   For token-based discovery, allow joining without --discovery-token-ca-cert-hash pinning.
-      --experimental-control-plane                    Create a new control plane instance on this node
-  -h, --help                                          help for download-certs
-      --tls-bootstrap-token string                    Specify the token used to temporarily authenticate with the Kubernetes Control Plane while joining the node.
-      --token string                                  Use this token for both discovery-token and tls-bootstrap-token when those values are not provided.
-```
-
-### 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;">[EXPERIMENTAL] The path to the 'real' host root filesystem.</td>
-    </tr>
-
-  </tbody>
-</table>
-
-
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_control-plane-prepare_kubeconfig.md.orig

@@ -1,48 +0,0 @@
-
-Generate the kubeconfig for the new control plane components
-
-### Synopsis
-
-Generate the kubeconfig for the new control plane components
-
-```
-kubeadm join phase control-plane-prepare kubeconfig [api-server-endpoint] [flags]
-```
-
-### Options
-
-```
-      --certificate-key string                        Use this key to decrypt the certificate secrets uploaded by init.
-      --config string                                 Path to kubeadm config file.
-      --control-plane                                 Create a new control plane instance on this node
-      --discovery-file string                         For file-based discovery, a file or URL from which to load cluster information.
-      --discovery-token string                        For token-based discovery, the token used to validate cluster information fetched from the API server.
-      --discovery-token-ca-cert-hash strings          For token-based discovery, validate that the root CA public key matches this hash (format: "<type>:<value>").
-      --discovery-token-unsafe-skip-ca-verification   For token-based discovery, allow joining without --discovery-token-ca-cert-hash pinning.
-      --experimental-control-plane                    Create a new control plane instance on this node
-  -h, --help                                          help for kubeconfig
-      --tls-bootstrap-token string                    Specify the token used to temporarily authenticate with the Kubernetes Control Plane while joining the node.
-      --token string                                  Use this token for both discovery-token and tls-bootstrap-token when those values are not provided.
-```
-
-### 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;">[EXPERIMENTAL] The path to the 'real' host root filesystem.</td>
-    </tr>
-
-  </tbody>
-</table>
-
-
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_kubelet-start.md.orig

@@ -1,116 +0,0 @@
-
-Write kubelet settings, certificates and (re)start the kubelet
-
-### Synopsis
-
-Write a file with KubeletConfiguration and an environment file with node specific kubelet settings, and then (re)start kubelet.
-
-```
-kubeadm join phase kubelet-start [api-server-endpoint] [flags]
-```
-
-### Options
-
-<table style="width: 100%; table-layout: fixed;">
-  <colgroup>
-    <col span="1" style="width: 10px;" />
-    <col span="1" />
-  </colgroup>
-  <tbody>
-
-    <tr>
-      <td colspan="2">--config string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Path to kubeadm config file.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--cri-socket string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Path to the CRI socket to connect. If empty kubeadm will try to auto-detect this value; use this option only if you have more than one CRI installed or if you have non-standard CRI socket.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--discovery-file string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">For file-based discovery, a file or URL from which to load cluster information.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--discovery-token string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">For token-based discovery, the token used to validate cluster information fetched from the API server.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--discovery-token-ca-cert-hash stringSlice</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">For token-based discovery, validate that the root CA public key matches this hash (format: "&lt;type&gt;:&lt;value&gt;").</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--discovery-token-unsafe-skip-ca-verification</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">For token-based discovery, allow joining without --discovery-token-ca-cert-hash pinning.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">-h, --help</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">help for kubelet-start</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--node-name string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Specify the node name.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--tls-bootstrap-token string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Specify the token used to temporarily authenticate with the Kubernetes Control Plane while joining the node.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--token string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Use this token for both discovery-token and tls-bootstrap-token when those values are not provided.</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;">[EXPERIMENTAL] The path to the 'real' host root filesystem.</td>
-    </tr>
-
-  </tbody>
-</table>
-
-
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_preflight.md.orig

@@ -1,61 +0,0 @@
-
-Run join pre-flight checks
-
-### Synopsis
-
-
-Run pre-flight checks for kubeadm join.
-
-```
-kubeadm join phase preflight [api-server-endpoint] [flags]
-```
-
-### Examples
-
-```
-  # Run join pre-flight checks using a config file.
-  kubeadm join phase preflight --config kubeadm-config.yml
-```
-
-### Options
-
-```
-      --apiserver-advertise-address string            If the node should host a new control plane instance, the IP address the API Server will advertise it's listening on. If not set the default network interface will be used.
-      --apiserver-bind-port int32                     If the node should host a new control plane instance, the port for the API Server to bind to. (default 6443)
-      --certificate-key string                        Use this key to decrypt the certificate secrets uploaded by init.
-      --config string                                 Path to kubeadm config file.
-      --control-plane                                 Create a new control plane instance on this node
-      --cri-socket string                             Path to the CRI socket to connect. If empty kubeadm will try to auto-detect this value; use this option only if you have more than one CRI installed or if you have non-standard CRI socket.
-      --discovery-file string                         For file-based discovery, a file or URL from which to load cluster information.
-      --discovery-token string                        For token-based discovery, the token used to validate cluster information fetched from the API server.
-      --discovery-token-ca-cert-hash strings          For token-based discovery, validate that the root CA public key matches this hash (format: "<type>:<value>").
-      --discovery-token-unsafe-skip-ca-verification   For token-based discovery, allow joining without --discovery-token-ca-cert-hash pinning.
-      --experimental-control-plane                    Create a new control plane instance on this node
-  -h, --help                                          help for preflight
-      --ignore-preflight-errors strings               A list of checks whose errors will be shown as warnings. Example: 'IsPrivilegedUser,Swap'. Value 'all' ignores errors from all checks.
-      --node-name string                              Specify the node name.
-      --tls-bootstrap-token string                    Specify the token used to temporarily authenticate with the Kubernetes Control Plane while joining the node.
-      --token string                                  Use this token for both discovery-token and tls-bootstrap-token when those values are not provided.
-```
-
-### 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;">[EXPERIMENTAL] The path to the 'real' host root filesystem.</td>
-    </tr>
-
-  </tbody>
-</table>
-
-
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_reset.md.orig

@@ -1,38 +0,0 @@
-
-Run this to revert any changes made to this host by 'kubeadm init' or 'kubeadm join'
-
-### Synopsis
-
-Run this to revert any changes made to this host by 'kubeadm init' or 'kubeadm join'
-
-The "reset" command executes the following phases:
-```
-preflight              Run reset pre-flight checks
-update-cluster-status  Remove this node from the ClusterStatus object.
-remove-etcd-member     Remove a local etcd member.
-cleanup-node           Run cleanup node.
-```
-
-
-```
-kubeadm reset [flags]
-```
-
-### Options
-
-```
-      --cert-dir string                   The path to the directory where the certificates are stored. If specified, clean this directory. (default "/etc/kubernetes/pki")
-      --cri-socket string                 Path to the CRI socket to connect. If empty kubeadm will try to auto-detect this value; use this option only if you have more than one CRI installed or if you have non-standard CRI socket.
-  -f, --force                             Reset the node without prompting for confirmation.
-  -h, --help                              help for reset
-      --ignore-preflight-errors strings   A list of checks whose errors will be shown as warnings. Example: 'IsPrivilegedUser,Swap'. Value 'all' ignores errors from all checks.
-      --kubeconfig string                 The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. (default "/etc/kubernetes/admin.conf")
-      --skip-phases strings               List of phases to be skipped
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_token.md.orig

@@ -1,47 +0,0 @@
-
-Manage bootstrap tokens
-
-### Synopsis
-
-
-This command manages bootstrap tokens. It is optional and needed only for advanced use cases.
-
-In short, bootstrap tokens are used for establishing bidirectional trust between a client and a server.
-A bootstrap token can be used when a client (for example a node that is about to join the cluster) needs
-to trust the server it is talking to. Then a bootstrap token with the "signing" usage can be used.
-bootstrap tokens can also function as a way to allow short-lived authentication to the API Server
-(the token serves as a way for the API Server to trust the client), for example for doing the TLS Bootstrap.
-
-What is a bootstrap token more exactly?
- - It is a Secret in the kube-system namespace of type "bootstrap.kubernetes.io/token".
- - A bootstrap token must be of the form "[a-z0-9]{6}.[a-z0-9]{16}". The former part is the public token ID,
-   while the latter is the Token Secret and it must be kept private at all circumstances!
- - The name of the Secret must be named "bootstrap-token-(token-id)".
-
-You can read more about bootstrap tokens here:
-  https://kubernetes.io/docs/admin/bootstrap-tokens/
-
-
-```
-kubeadm token [flags]
-```
-
-### Options
-
-```
-      --dry-run             Whether to enable dry-run mode or not
-  -h, --help                help for token
-      --kubeconfig string   The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. (default "/etc/kubernetes/admin.conf")
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-
-  </tbody>
-</table>
-
-
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_token_create.md.orig

@@ -1,38 +0,0 @@
-
-Create bootstrap tokens on the server
-
-### Synopsis
-
-
-This command will create a bootstrap token for you.
-You can specify the usages for this token, the "time to live" and an optional human friendly description.
-
-The [token] is the actual token to write.
-This should be a securely generated random token of the form "[a-z0-9]{6}.[a-z0-9]{16}".
-If no [token] is given, kubeadm will generate a random token instead.
-
-
-```
-kubeadm token create [token]
-```
-
-### Options
-
-```
-      --config string        Path to a kubeadm configuration file.
-      --description string   A human friendly description of how this token is used.
-      --groups strings       Extra groups that this token will authenticate as when used for authentication. Must match "\\Asystem:bootstrappers:[a-z0-9:-]{0,255}[a-z0-9]\\z" (default [system:bootstrappers:kubeadm:default-node-token])
-  -h, --help                 help for create
-      --print-join-command   Instead of printing only the token, print the full 'kubeadm join' flag needed to join the cluster using the token.
-      --ttl duration         The duration before the token is automatically deleted (e.g. 1s, 2m, 3h). If set to '0', the token will never expire (default 24h0m0s)
-      --usages strings       Describes the ways in which this token can be used. You can pass --usages multiple times or provide a comma separated list of options. Valid options: [signing,authentication] (default [signing,authentication])
-```
-
-### Options inherited from parent commands
-
-```
-      --dry-run             Whether to enable dry-run mode or not
-      --kubeconfig string   The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. (default "/etc/kubernetes/admin.conf")
-      --rootfs string       [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_token_delete.md.orig

@@ -1,30 +0,0 @@
-
-Delete bootstrap tokens on the server
-
-### Synopsis
-
-
-This command will delete a list of bootstrap tokens for you.
-
-The [token-value] is the full Token of the form "[a-z0-9]{6}.[a-z0-9]{16}" or the
-Token ID of the form "[a-z0-9]{6}" to delete.
-
-
-```
-kubeadm token delete [token-value] ...
-```
-
-### Options
-
-```
-  -h, --help   help for delete
-```
-
-### Options inherited from parent commands
-
-```
-      --dry-run             Whether to enable dry-run mode or not
-      --kubeconfig string   The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. (default "/etc/kubernetes/admin.conf")
-      --rootfs string       [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_token_generate.md.orig

@@ -1,35 +0,0 @@
-
-Generate and print a bootstrap token, but do not create it on the server
-
-### Synopsis
-
-
-This command will print out a randomly-generated bootstrap token that can be used with
-the "init" and "join" commands.
-
-You don't have to use this command in order to generate a token. You can do so
-yourself as long as it is in the format "[a-z0-9]{6}.[a-z0-9]{16}". This
-command is provided for convenience to generate tokens in the given format.
-
-You can also use "kubeadm init" without specifying a token and it will
-generate and print one for you.
-
-
-```
-kubeadm token generate [flags]
-```
-
-### Options
-
-```
-  -h, --help   help for generate
-```
-
-### Options inherited from parent commands
-
-```
-      --dry-run             Whether to enable dry-run mode or not
-      --kubeconfig string   The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. (default "/etc/kubernetes/admin.conf")
-      --rootfs string       [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_token_list.md.orig

@@ -1,27 +0,0 @@
-
-List bootstrap tokens on the server
-
-### Synopsis
-
-
-This command will list all bootstrap tokens for you.
-
-
-```
-kubeadm token list [flags]
-```
-
-### Options
-
-```
-  -h, --help   help for list
-```
-
-### Options inherited from parent commands
-
-```
-      --dry-run             Whether to enable dry-run mode or not
-      --kubeconfig string   The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. (default "/etc/kubernetes/admin.conf")
-      --rootfs string       [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_upgrade_apply.md.orig

@@ -1,36 +0,0 @@
-
-Upgrade your Kubernetes cluster to the specified version
-
-### Synopsis
-
-Upgrade your Kubernetes cluster to the specified version
-
-```
-kubeadm upgrade apply [version]
-```
-
-### Options
-
-```
-      --allow-experimental-upgrades        Show unstable versions of Kubernetes as an upgrade alternative and allow upgrading to an alpha/beta/release candidate versions of Kubernetes.
-      --allow-release-candidate-upgrades   Show release candidate versions of Kubernetes as an upgrade alternative and allow upgrading to a release candidate versions of Kubernetes.
-      --certificate-renewal                Perform the renewal of certificates used by component changed during upgrades. (default true)
-      --config string                      Path to a kubeadm configuration file.
-      --dry-run                            Do not change any state, just output what actions would be performed.
-      --etcd-upgrade                       Perform the upgrade of etcd. (default true)
-      --feature-gates string               A set of key=value pairs that describe feature gates for various features. No feature gates are available in this release.
-  -f, --force                              Force upgrading although some requirements might not be met. This also implies non-interactive mode.
-  -h, --help                               help for apply
-      --ignore-preflight-errors strings    A list of checks whose errors will be shown as warnings. Example: 'IsPrivilegedUser,Swap'. Value 'all' ignores errors from all checks.
-      --image-pull-timeout duration        The maximum amount of time to wait for the control plane pods to be downloaded. (default 15m0s)
-      --kubeconfig string                  The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. (default "/etc/kubernetes/admin.conf")
-      --print-config                       Specifies whether the configuration file that will be used in the upgrade should be printed or not.
-  -y, --yes                                Perform the upgrade and do not prompt for confirmation (non-interactive mode).
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_upgrade_node_config.md.orig

@@ -1,86 +0,0 @@
-
-Downloads the kubelet configuration from the cluster ConfigMap kubelet-config-1.X, where X is the minor version of the kubelet.
-
-### Synopsis
-
-
-Downloads the kubelet configuration from a ConfigMap of the form "kubelet-config-1.X" in the cluster, where X is the minor version of the kubelet. kubeadm uses the --kubelet-version parameter to determine what the desired kubelet version is. Give
-
-```
-kubeadm upgrade node config [flags]
-```
-
-### Examples
-
-```
-  # Downloads the kubelet configuration from the ConfigMap in the cluster. Uses a specific desired kubelet version.
-  kubeadm upgrade node config --kubelet-version 1.14.0
-  
-  # Simulates the downloading of the kubelet configuration from the ConfigMap in the cluster with a specific desired
-  # version. Does not change any state locally on the node.
-  kubeadm upgrade node config --kubelet-version 1.14.0 --dry-run
-```
-
-### Options
-
-<table style="width: 100%; table-layout: fixed;">
-  <colgroup>
-    <col span="1" style="width: 10px;" />
-    <col span="1" />
-  </colgroup>
-  <tbody>
-
-    <tr>
-      <td colspan="2">--dry-run</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Do not change any state, just output the actions that would be performed.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">-h, --help</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">help for config</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--kubeconfig string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "/etc/kubernetes/admin.conf"</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--kubelet-version string</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The *desired* version for the kubelet after the upgrade.</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;">[EXPERIMENTAL] The path to the 'real' host root filesystem.</td>
-    </tr>
-
-  </tbody>
-</table>
-
-
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_upgrade_node_experimental-control-plane.md.orig

@@ -1,86 +0,0 @@
-
-Upgrades the control plane instance deployed on this node. IMPORTANT. This command should be executed after executing `kubeadm upgrade apply` on another control plane instance
-
-### Synopsis
-
-
-Downloads the kubelet configuration from a ConfigMap of the form "kubelet-config-1.X" in the cluster, where X is the minor version of the kubelet. kubeadm uses the --kubelet-version parameter to determine what the desired kubelet version is. Give
-
-```
-kubeadm upgrade node experimental-control-plane [flags]
-```
-
-### Examples
-
-```
-  # Downloads the kubelet configuration from the ConfigMap in the cluster. Uses a specific desired kubelet version.
-  kubeadm upgrade node config --kubelet-version 1.14.0
-  
-  # Simulates the downloading of the kubelet configuration from the ConfigMap in the cluster with a specific desired
-  # version. Does not change any state locally on the node.
-  kubeadm upgrade node config --kubelet-version 1.14.0 --dry-run
-```
-
-### Options
-
-<table style="width: 100%; table-layout: fixed;">
-  <colgroup>
-    <col span="1" style="width: 10px;" />
-    <col span="1" />
-  </colgroup>
-  <tbody>
-
-    <tr>
-      <td colspan="2">--dry-run</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Do not change any state, just output the actions that would be performed.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--etcd-upgrade&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: true</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">Perform the upgrade of etcd.</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">-h, --help</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">help for experimental-control-plane</td>
-    </tr>
-
-    <tr>
-      <td colspan="2">--kubeconfig string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "/etc/kubernetes/admin.conf"</td>
-    </tr>
-    <tr>
-      <td></td><td style="line-height: 130%; word-wrap: break-word;">The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file.</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;">[EXPERIMENTAL] The path to the 'real' host root filesystem.</td>
-    </tr>
-
-  </tbody>
-</table>
-
-
-

content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_upgrade_plan.md.orig

@@ -1,30 +0,0 @@
-
-Check which versions are available to upgrade to and validate whether your current cluster is upgradeable. To skip the internet check, pass in the optional [version] parameter
-
-### Synopsis
-
-Check which versions are available to upgrade to and validate whether your current cluster is upgradeable. To skip the internet check, pass in the optional [version] parameter
-
-```
-kubeadm upgrade plan [version] [flags]
-```
-
-### Options
-
-```
-      --allow-experimental-upgrades        Show unstable versions of Kubernetes as an upgrade alternative and allow upgrading to an alpha/beta/release candidate versions of Kubernetes.
-      --allow-release-candidate-upgrades   Show release candidate versions of Kubernetes as an upgrade alternative and allow upgrading to a release candidate versions of Kubernetes.
-      --config string                      Path to a kubeadm configuration file.
-      --feature-gates string               A set of key=value pairs that describe feature gates for various features. No feature gates are available in this release.
-  -h, --help                               help for plan
-      --ignore-preflight-errors strings    A list of checks whose errors will be shown as warnings. Example: 'IsPrivilegedUser,Swap'. Value 'all' ignores errors from all checks.
-      --kubeconfig string                  The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. (default "/etc/kubernetes/admin.conf")
-      --print-config                       Specifies whether the configuration file that will be used in the upgrade should be printed or not.
-```
-
-### Options inherited from parent commands
-
-```
-      --rootfs string   [EXPERIMENTAL] The path to the 'real' host root filesystem.
-```
-

content/en/docs/reference/setup-tools/kubeadm/kubeadm-init.md.orig

@@ -1,363 +0,0 @@
----
-reviewers:
-- mikedanese
-- luxas
-- jbeda
-title: kubeadm init
-content_template: templates/concept
-weight: 20
----
-{{% capture overview %}}
-This command initializes a Kubernetes control-plane node.
-{{% /capture %}}
-
-{{% capture body %}}
-
-{{< include "generated/kubeadm_init.md" >}}
-
-### Init workflow {#init-workflow}
-`kubeadm init` bootstraps a Kubernetes control-plane node by executing the
-following steps:
-
-1. Runs a series of pre-flight checks to validate the system state
-   before making changes. Some checks only trigger warnings, others are
-   considered errors and will exit kubeadm until the problem is corrected or the
-   user specifies `--ignore-preflight-errors=<list-of-errors>`.
-
-1. Generates a self-signed CA (or using an existing one if provided) to set up
-   identities for each component in the cluster. If the user has provided their
-   own CA cert and/or key by dropping it in the cert directory configured via `--cert-dir`
-   (`/etc/kubernetes/pki` by default) this step is skipped as described in the
-   [Using custom certificates](#custom-certificates) document.
-   The APIServer certs will have additional SAN entries for any `--apiserver-cert-extra-sans` arguments, lowercased if necessary.
-
-1. Writes kubeconfig files in `/etc/kubernetes/`  for
-   the kubelet, the controller-manager and the scheduler to use to connect to the
-   API server, each with its own identity, as well as an additional
-   kubeconfig file for administration named `admin.conf`.
-
-1. Generates static Pod manifests for the API server,
-   controller manager and scheduler. In case an external etcd is not provided,
-   an additional static Pod manifest is generated for etcd.
-
-   Static Pod manifests are written to `/etc/kubernetes/manifests`; the kubelet
-   watches this directory for Pods to create on startup.
-
-   Once control plane Pods are up and running, the `kubeadm init` sequence can continue.
-
-1. Apply labels and taints to the control-plane node so that no additional workloads will
-   run there.
-
-1. Generates the token that additional nodes can use to register
-   themselves with a control-plane in the future. Optionally, the user can provide a
-   token via `--token`, as described in the
-   [kubeadm token](/docs/reference/setup-tools/kubeadm/kubeadm-token/) docs.
-
-1. Makes all the necessary configurations for allowing node joining with the
-   [Bootstrap Tokens](/docs/reference/access-authn-authz/bootstrap-tokens/) and
-   [TLS Bootstrap](/docs/reference/command-line-tools-reference/kubelet-tls-bootstrapping/)
-   mechanism:
-
-   - Write a ConfigMap for making available all the information required
-     for joining, and set up related RBAC access rules.
-
-   - Let Bootstrap Tokens access the CSR signing API.
-
-   - Configure auto-approval for new CSR requests.
-
-   See [kubeadm join](/docs/reference/setup-tools/kubeadm/kubeadm-join/) for additional info.
-
-1. Installs a DNS server (CoreDNS) and the kube-proxy addon components via the API server.
-   In Kubernetes version 1.11 and later CoreDNS is the default DNS server.
-   To install kube-dns instead of CoreDNS, the DNS addon has to be configured in the kubeadm `ClusterConfiguration`. For more information about the configuration see the section
-   `Using kubeadm init with a configuration file` below.
-   Please note that although the DNS server is deployed, it will not be scheduled until CNI is installed.
-
-### Using init phases with kubeadm {#init-phases}
-
-Kubeadm allows you create a control-plane node in phases. In 1.13 the `kubeadm init phase` command has graduated to GA from it’s previous alpha state under `kubeadm alpha phase`.
-
-To view the ordered list of phases and sub-phases you can call `kubeadm init --help`. The list will be located at the top of the help screen and each phase will have a description next to it.
-Note that by calling `kubeadm init` all of the phases and sub-phases will be executed in this exact order.
-
-Some phases have unique flags, so if you want to have a look at the list of available options add `--help`, for example:
-
-```shell
-sudo kubeadm init phase control-plane controller-manager --help
-```
-
-You can also use `--help` to see the list of sub-phases for a certain parent phase:
-
-```shell
-sudo kubeadm init phase control-plane --help
-```
-
-`kubeadm init` also exposes a flag called `--skip-phases` that can be used to skip certain phases. The flag accepts a list of phase names and the names can be taken from the above ordered list.
-
-An example:
-
-```shell
-sudo kubeadm init phase control-plane all --config=configfile.yaml
-sudo kubeadm init phase etcd local --config=configfile.yaml
-# you can now modify the control plane and etcd manifest files
-sudo kubeadm init --skip-phases=control-plane,etcd --config=configfile.yaml
-```
-
-What this example would do is write the manifest files for the control plane and etcd in `/etc/kubernetes/manifests` based on the configuration in `configfile.yaml`. This allows you to modify the files and then skip these phases using `--skip-phases`. By calling the last command you will create a control plane node with the custom manifest files.
-
-### Using kubeadm init with a configuration file {#config-file}
-
-{{< caution >}}
-The config file is still considered beta and may change in future versions.
-{{< /caution >}}
-
-It's possible to configure `kubeadm init` with a configuration file instead of command
-line flags, and some more advanced features may only be available as
-configuration file options. This file is passed in the `--config` option.
-
-In Kubernetes 1.11 and later, the default configuration can be printed out using the
-[kubeadm config print](/docs/reference/setup-tools/kubeadm/kubeadm-config/) command.
-
-It is **recommended** that you migrate your old `v1beta1` configuration to `v1beta2` using
-the [kubeadm config migrate](/docs/reference/setup-tools/kubeadm/kubeadm-config/) command.
-
-For more details on each field in the `v1beta2` configuration you can navigate to our
-[API reference pages](https://godoc.org/k8s.io/kubernetes/cmd/kubeadm/app/apis/kubeadm/v1beta2).
-
-### Adding kube-proxy parameters {#kube-proxy}
-
-For information about kube-proxy parameters in the kubeadm configuration see:
-- [kube-proxy](https://godoc.org/k8s.io/kubernetes/pkg/proxy/apis/config#KubeProxyConfiguration)
-
-For information about enabling IPVS mode with kubeadm see:
-- [IPVS](https://github.com/kubernetes/kubernetes/blob/master/pkg/proxy/ipvs/README.md)
-
-### Passing custom flags to control plane components {#control-plane-flags}
-
-For information about passing flags to control plane components see:
-- [control-plane-flags](/docs/setup/production-environment/tools/kubeadm/control-plane-flags/)
-
-### Using custom images {#custom-images}
-
-By default, kubeadm pulls images from `k8s.gcr.io`, unless
-the requested Kubernetes version is a CI version. In this case,
-`gcr.io/kubernetes-ci-images` is used.
-
-You can override this behavior by using [kubeadm with a configuration file](#config-file).
-Allowed customization are:
-
-* To provide an alternative `imageRepository` to be used instead of
-  `k8s.gcr.io`.
-* To set `useHyperKubeImage` to `true` to use the HyperKube image.
-* To provide a specific `imageRepository` and `imageTag` for etcd or DNS add-on.
-
-Please note that the configuration field `kubernetesVersion` or the command line flag
-`--kubernetes-version` affect the version of the images.
-
-### Uploading control-plane certificates to the cluster
-
-By adding the flag `--upload-certs` to `kubeadm init` you can temporary upload
-the control-plane certificates to a Secret in the cluster. Please note that this Secret
-will expire automatically after 2 hours. The certificates are encrypted using
-a 32byte key that can be specified using `--certificate-key`. The same key can be used
-to download the certificates when additional control-plane nodes are joining, by passing
-`--control-plane` and `--certificate-key` to `kubeadm join`.
-
-The following phase command can be used to re-upload the certificates after expiration:
-
-```
-kubeadm init phase upload-certs --upload-certs --certificate-key=SOME_VALUE
-```
-
-If the flag `--certificate-key` is not passed to `kubeadm init` and
-`kubeadm init phase upload-certs` a new key will be generated automatically.
-
-The following command can be used to generate a new key on demand:
-
-```
-kubeadm alpha certs certificate-key
-```
-
-### Using custom certificates {#custom-certificates}
-
-By default, kubeadm generates all the certificates needed for a cluster to run.
-You can override this behavior by providing your own certificates.
-
-To do so, you must place them in whatever directory is specified by the
-`--cert-dir` flag or `CertificatesDir` configuration file key. By default this
-is `/etc/kubernetes/pki`.
-
-If a given certificate and private key pair exists, kubeadm skips the
-generation step and existing files are used for the prescribed
-use case. This means you can, for example, copy an existing CA into `/etc/kubernetes/pki/ca.crt`
-and `/etc/kubernetes/pki/ca.key`, and kubeadm will use this CA for signing the rest
-of the certs.
-
-#### External CA mode {#external-ca-mode}
-
-It is also possible to provide just the `ca.crt` file and not the
-`ca.key` file (this is only available for the root CA file, not other cert pairs).
-If all other certificates and kubeconfig files are in place, kubeadm recognizes
-this condition and activates the "External CA" mode. kubeadm will proceed without the
-CA key on disk.
-
-Instead, run the controller-manager standalone with `--controllers=csrsigner` and
-point to the CA certificate and key.
-
-### Managing the kubeadm drop-in file for the kubelet {#kubelet-drop-in}
-
-The kubeadm package ships with configuration for how the kubelet should
-be run. Note that the `kubeadm` CLI command never touches this drop-in file.
-This drop-in file belongs to the kubeadm deb/rpm package.
-
-This is what it looks like:
-
-
-```
-[Service]
-Environment="KUBELET_KUBECONFIG_ARGS=--bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf
---kubeconfig=/etc/kubernetes/kubelet.conf"
-Environment="KUBELET_CONFIG_ARGS=--config=/var/lib/kubelet/config.yaml"
-# This is a file that "kubeadm init" and "kubeadm join" generates at runtime, populating
-the KUBELET_KUBEADM_ARGS variable dynamically
-EnvironmentFile=-/var/lib/kubelet/kubeadm-flags.env
-# This is a file that the user can use for overrides of the kubelet args as a last resort. Preferably,
-#the user should use the .NodeRegistration.KubeletExtraArgs object in the configuration files instead.
-# KUBELET_EXTRA_ARGS should be sourced from this file.
-EnvironmentFile=-/etc/default/kubelet
-ExecStart=
-ExecStart=/usr/bin/kubelet $KUBELET_KUBECONFIG_ARGS $KUBELET_CONFIG_ARGS $KUBELET_KUBEADM_ARGS $KUBELET_EXTRA_ARGS
-```
-
-Here's a breakdown of what/why:
-
-* `--bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf` path to a kubeconfig
-   file that is used to get client certificates for kubelet during node join.
-   On success, a kubeconfig file is written to the path specified by `--kubeconfig`.
-* `--kubeconfig=/etc/kubernetes/kubelet.conf` points to the kubeconfig file that
-   tells the kubelet where the API server is. This file also has the kubelet's
-   credentials.
-* `--pod-manifest-path=/etc/kubernetes/manifests` specifies from where to read
-   static Pod manifests used for starting the control plane.
-* `--allow-privileged=true` allows this kubelet to run privileged Pods.
-* `--network-plugin=cni` uses CNI networking.
-* `--cni-conf-dir=/etc/cni/net.d` specifies where to look for the
-   [CNI spec file(s)](https://github.com/containernetworking/cni/blob/master/SPEC.md).
-* `--cni-bin-dir=/opt/cni/bin` specifies where to look for the actual CNI binaries.
-* `--cluster-dns=10.96.0.10` use this cluster-internal DNS server for `nameserver`
-   entries in Pods' `/etc/resolv.conf`.
-* `--cluster-domain=cluster.local` uses this cluster-internal DNS domain for
-   `search` entries in Pods' `/etc/resolv.conf`.
-* `--client-ca-file=/etc/kubernetes/pki/ca.crt` authenticates requests to the Kubelet
-   API using this CA certificate.
-* `--authorization-mode=Webhook` authorizes requests to the Kubelet API by `POST`-ing
-   a `SubjectAccessReview` to the API server.
-* `--rotate-certificates` auto rotate the kubelet client certificates by requesting new
-   certificates from the `kube-apiserver` when the certificate expiration approaches.
-* `--cert-dir`the directory where the TLS certs are located.
-
-### Use kubeadm with CRI runtimes
-
-Since v1.6.0, Kubernetes has enabled the use of CRI, Container Runtime Interface, by default.
-The container runtime used by default is Docker, which is enabled through the built-in
-`dockershim` CRI implementation inside of the `kubelet`.
-
-Other CRI-based runtimes include:
-
-- [cri-containerd](https://github.com/containerd/cri-containerd)
-- [cri-o](https://github.com/kubernetes-incubator/cri-o)
-- [frakti](https://github.com/kubernetes/frakti)
-- [rkt](https://github.com/kubernetes-incubator/rktlet)
-
-Refer to the [CRI installation instructions](/docs/setup/cri) for more information.
-
-After you have successfully installed `kubeadm` and `kubelet`, execute
-these two additional steps:
-
-1. Install the runtime shim on every node, following the installation
-   document in the runtime shim project listing above.
-
-1. Configure kubelet to use the remote CRI runtime. Please remember to change
-   `RUNTIME_ENDPOINT` to your own value like `/var/run/{your_runtime}.sock`:
-
-```shell
-cat > /etc/systemd/system/kubelet.service.d/20-cri.conf <<EOF
-[Service]
-Environment="KUBELET_EXTRA_ARGS=--container-runtime=remote --container-runtime-endpoint=$RUNTIME_ENDPOINT"
-EOF
-systemctl daemon-reload
-```
-
-Now `kubelet` is ready to use the specified CRI runtime, and you can continue
-with the `kubeadm init` and `kubeadm join` workflow to deploy Kubernetes cluster.
-
-You may also want to set `--cri-socket` to `kubeadm init` and `kubeadm reset` when
-using an external CRI implementation.
-
-### Setting the node name
-
-By default, `kubeadm` assigns a node name based on a machine's host address. You can override this setting with the `--node-name`flag.
-The flag passes the appropriate [`--hostname-override`](/docs/reference/command-line-tools-reference/kubelet/#options)
-to the kubelet.
-
-Be aware that overriding the hostname can [interfere with cloud providers](https://github.com/kubernetes/website/pull/8873).
-
-### Running kubeadm without an internet connection
-
-For running kubeadm without an internet connection you have to pre-pull the required control-plane images.
-
-In Kubernetes 1.11 and later, you can list and pull the images using the `kubeadm config images` sub-command:
-
-```shell
-kubeadm config images list
-kubeadm config images pull
-```
-
-In Kubernetes 1.12 and later, the `k8s.gcr.io/kube-*`, `k8s.gcr.io/etcd` and `k8s.gcr.io/pause` images
-don't require an `-${ARCH}` suffix.
-
-### Automating kubeadm
-
-Rather than copying the token you obtained from `kubeadm init` to each node, as
-in the [basic kubeadm tutorial](/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/), you can parallelize the
-token distribution for easier automation. To implement this automation, you must
-know the IP address that the control-plane node will have after it is started.
-
-1.  Generate a token. This token must have the form  `<6 character string>.<16
-    character string>`.  More formally, it must match the regex:
-    `[a-z0-9]{6}\.[a-z0-9]{16}`.
-
-    kubeadm can generate a token for you:
-
-    ```shell
-    kubeadm token generate
-    ```
-
-1.  Start both the control-plane node and the worker nodes concurrently with this token.
-    As they come up they should find each other and form the cluster.  The same
-    `--token` argument can be used on both `kubeadm init` and `kubeadm join`.
-
-1.  Similar can be done for `--certificate-key` when joining additional control-plane
-    nodes. The key can be generated using:
-
-    ```shell
-    kubeadm alpha certs certificate-key
-    ```
-
-Once the cluster is up, you can grab the admin credentials from the control-plane node
-at `/etc/kubernetes/admin.conf` and use that to talk to the cluster.
-
-Note that this style of bootstrap has some relaxed security guarantees because
-it does not allow the root CA hash to be validated with
-`--discovery-token-ca-cert-hash` (since it's not generated when the nodes are
-provisioned). For details, see the [kubeadm join](/docs/reference/setup-tools/kubeadm/kubeadm-join/).
-
-{{% /capture %}}
-
-{{% capture whatsnext %}}
-* [kubeadm init phase](/docs/reference/setup-tools/kubeadm/kubeadm-init-phase/) to understand more about
-`kubeadm init` phases
-* [kubeadm join](/docs/reference/setup-tools/kubeadm/kubeadm-join/) to bootstrap a Kubernetes worker node and join it to the cluster
-* [kubeadm upgrade](/docs/reference/setup-tools/kubeadm/kubeadm-upgrade/) to upgrade a Kubernetes cluster to a newer version
-* [kubeadm reset](/docs/reference/setup-tools/kubeadm/kubeadm-reset/) to revert any changes made to this host by `kubeadm init` or `kubeadm join`
-{{% /capture %}}

content/en/docs/setup/production-environment/tools/kubeadm/control-plane-flags.md.orig

@@ -1,87 +0,0 @@
----
-reviewers:
-- sig-cluster-lifecycle
-title: Customizing control plane configuration with kubeadm
-content_template: templates/concept
-weight: 40
----
-
-{{% capture overview %}}
-
-{{< feature-state for_k8s_version="1.12" state="stable" >}}
-
-The kubeadm `ClusterConfiguration` object exposes the field `extraArgs` that can override the default flags passed to control plane
-components such as the APIServer, ControllerManager and Scheduler. The components are defined using the following fields:
-
-- `apiServer`
-- `controllerManager`
-- `scheduler`
-
-The `extraArgs` field consist of `key: value` pairs. To override a flag for a control plane component:
-
-1.  Add the appropriate fields to your configuration.
-2.  Add the flags to override to the field.
-
-For more details on each field in the configuration you can navigate to our
-[API reference pages](https://godoc.org/k8s.io/kubernetes/cmd/kubeadm/app/apis/kubeadm/v1beta2#ClusterConfiguration).
-
-{{% /capture %}}
-
-{{% capture body %}}
-
-## APIServer flags
-
-For details, see the [reference documentation for kube-apiserver](/docs/reference/command-line-tools-reference/kube-apiserver/).
-
-Example usage:
-```yaml
-apiVersion: kubeadm.k8s.io/v1beta2
-kind: ClusterConfiguration
-kubernetesVersion: v1.13.0
-metadata:
-  name: 1.13-sample
-apiServer:
-  extraArgs:
-    advertise-address: 192.168.0.103
-    anonymous-auth: false
-    enable-admission-plugins: AlwaysPullImages,DefaultStorageClass
-    audit-log-path: /home/johndoe/audit.log
-```
-
-## ControllerManager flags
-
-For details, see the [reference documentation for kube-controller-manager](/docs/reference/command-line-tools-reference/kube-controller-manager/).
-
-Example usage:
-```yaml
-apiVersion: kubeadm.k8s.io/v1beta2
-kind: ClusterConfiguration
-kubernetesVersion: v1.13.0
-metadata:
-  name: 1.13-sample
-controllerManager:
-  extraArgs:
-    cluster-signing-key-file: /home/johndoe/keys/ca.key
-    bind-address: 0.0.0.0
-    deployment-controller-sync-period: 50
-```
-
-## Scheduler flags
-
-For details, see the [reference documentation for kube-scheduler](/docs/reference/command-line-tools-reference/kube-scheduler/).
-
-Example usage:
-```yaml
-apiVersion: kubeadm.k8s.io/v1beta2
-kind: ClusterConfiguration
-kubernetesVersion: v1.13.0
-metadata:
-  name: 1.13-sample
-scheduler:
-  extraArgs:
-    address: 0.0.0.0
-    config: /home/johndoe/schedconfig.yaml
-    kubeconfig: /home/johndoe/kubeconfig.yaml
-```
-
-{{% /capture %}}