OPENSHIFT START KUBERNETES(1)

NAME

openshift start kubernetes controller-manager - Launch Kubernetes controller manager (kube-controller-manager)

SYNOPSIS

openshift start kubernetes controller-manager [OPTIONS]

DESCRIPTION

Start Kubernetes controller manager

This command launches an instance of the Kubernetes controller-manager (kube-controller-manager).

OPTIONS

--address=0.0.0.0
    The IP address to serve on (set to 0.0.0.0 for all interfaces)

--allocate-node-cidrs=false
    Should CIDRs for Pods be allocated and set on the cloud provider.

--attach-detach-reconcile-sync-period=0
    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.

--cloud-config=""
    The path to the cloud provider configuration file. Empty string for no configuration file.

--cloud-provider=""
    The provider for cloud services. Empty string for no provider.

--cluster-cidr=""
    CIDR Range for Pods in cluster.

--cluster-name="kubernetes"
    The instance prefix for the cluster

--cluster-signing-cert-file="/etc/kubernetes/ca/ca.pem"
    Filename containing a PEM-encoded X509 CA certificate used to issue cluster-scoped certificates

--cluster-signing-key-file="/etc/kubernetes/ca/ca.key"
    Filename containing a PEM-encoded RSA or ECDSA private key used to sign cluster-scoped certificates

--concurrent-deployment-syncs=5
    The number of deployment objects that are allowed to sync concurrently. Larger number = more responsive deployments, but more CPU (and network) load

--concurrent-endpoint-syncs=5
    The number of endpoint syncing operations that will be done concurrently. Larger number = faster endpoint updating, but more CPU (and network) load

--concurrent-gc-syncs=20
    The number of garbage collector workers that are allowed to sync concurrently.

--concurrent-namespace-syncs=2
    The number of namespace objects that are allowed to sync concurrently. Larger number = more responsive namespace termination, but more CPU (and network) load

--concurrent-rc-syncs=5
    The number of replication controllers that are allowed to sync concurrently. Larger number = more responsive replica management, but more CPU (and network) load

--concurrent-replicaset-syncs=5
    The number of replica sets that are allowed to sync concurrently. Larger number = more responsive replica management, but more CPU (and network) load

--concurrent-resource-quota-syncs=5
    The number of resource quotas that are allowed to sync concurrently. Larger number = more responsive quota management, but more CPU (and network) load

--concurrent-service-syncs=1
    The number of services that are allowed to sync concurrently. Larger number = more responsive service management, but more CPU (and network) load

--concurrent-serviceaccount-token-syncs=5
    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

--configure-cloud-routes=true
    Should CIDRs allocated by allocate-node-cidrs be configured on the cloud provider.

--controller-start-interval=0
    Interval between starting controller managers.

--daemonset-lookup-cache-size=1024
    The the size of lookup cache for daemonsets. Larger number = more responsive daemonsets, but more MEM load.

--deleting-pods-burst=0
    Number of nodes on which pods are bursty deleted in case of node failure. For more details look into RateLimiter.

--deleting-pods-qps=0.1
    Number of nodes per second on which pods are deleted in case of node failure.

--deployment-controller-sync-period=0
    Period for syncing the deployments.

--disable-attach-detach-reconcile-sync=false
    Disable volume attach detach reconciler sync. Disabling this may cause volumes to be mismatched with pods. Use wisely.

--enable-dynamic-provisioning=true
    Enable dynamic provisioning for environments that support it.

--enable-garbage-collector=true
    Enables the generic garbage collector. MUST be synced with the corresponding flag of the kube-apiserver.

--enable-hostpath-provisioner=false
    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.

--feature-gates=
    A set of key=value pairs that describe feature gates for alpha/experimental features. Options are: AllAlpha=true|false (ALPHA - default=false) AllowExtTrafficLocalEndpoints=true|false (BETA - default=true) AppArmor=true|false (BETA - default=true) DynamicKubeletConfig=true|false (ALPHA - default=false) DynamicVolumeProvisioning=true|false (ALPHA - default=true) ExperimentalHostUserNamespaceDefaulting=true|false (ALPHA - default=false) StreamingProxyRedirects=true|false (ALPHA - default=false)

--flex-volume-plugin-dir="/usr/libexec/kubernetes/kubelet-plugins/volume/exec/"
    Full path of the directory in which the flex volume plugin should search for additional third party volume plugins.

--horizontal-pod-autoscaler-sync-period=0
    The period for syncing the number of pods in horizontal pod autoscaler.

--insecure-experimental-approve-all-kubelet-csrs-for-group=""
    The group for which the controller-manager will auto approve all CSRs for kubelet client certificates.

--kube-api-burst=30
    Burst to use while talking with kubernetes apiserver

--kube-api-content-type="application/vnd.kubernetes.protobuf"
    Content type of requests sent to apiserver.

--kube-api-qps=20
    QPS to use while talking with kubernetes apiserver

--kubeconfig=""
    Path to kubeconfig file with authorization and master location information.

--large-cluster-size-threshold=50
    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.

--leader-elect=true
    Start a leader election client and gain leadership before executing the main loop. Enable this when running replicated components for high availability.

--leader-elect-lease-duration=0
    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.

--leader-elect-renew-deadline=0
    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.

--leader-elect-retry-period=0
    The duration the clients should wait between attempting acquisition and renewal of a leadership. This is only applicable if leader election is enabled.

--master=""
    The address of the Kubernetes API server (overrides any value in kubeconfig)

--min-resync-period=0
    The resync period in reflectors will be random between MinResyncPeriod and 2*MinResyncPeriod

--namespace-sync-period=0
    The period for syncing namespace life-cycle updates

--node-cidr-mask-size=24
    Mask size for node cidr in cluster.

--node-eviction-rate=0.1
    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.

--node-monitor-grace-period=0
    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.

--node-monitor-period=0
    The period for syncing NodeStatus in NodeController.

--node-startup-grace-period=0
    Amount of time which we allow starting Node to be unresponsive before marking it unhealthy.

--node-sync-period=0
    This flag is deprecated and will be removed in future releases. See node-monitor-period for Node health checking or route-reconciliation-period for cloud provider's route configuration settings.

--pod-eviction-timeout=0
    The grace period for deleting pods on failed nodes.

--port=10252
    The port that the controller-manager's http service runs on

--profiling=true
    Enable profiling via web interface host:port/debug/pprof/

--pv-recycler-increment-timeout-nfs=30
    the increment of time added per Gi to ActiveDeadlineSeconds for an NFS scrubber pod

--pv-recycler-minimum-timeout-hostpath=60
    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.

--pv-recycler-minimum-timeout-nfs=300
    The minimum ActiveDeadlineSeconds to use for an NFS Recycler pod

--pv-recycler-pod-template-filepath-hostpath=""
    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.

--pv-recycler-pod-template-filepath-nfs=""
    The file path to a pod definition used as a template for NFS persistent volume recycling

--pv-recycler-timeout-increment-hostpath=30
    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.

--pvclaimbinder-sync-period=0
    The period for syncing persistent volumes and persistent volume claims

--register-retry-count=10
    The number of retries for initial node registration. Retry interval equals node-sync-period.

--replicaset-lookup-cache-size=4096
    The the size of lookup cache for replicatsets. Larger number = more responsive replica management, but more MEM load.

--replication-controller-lookup-cache-size=4096
    The the size of lookup cache for replication controllers. Larger number = more responsive replica management, but more MEM load.

--resource-quota-sync-period=0
    The period for syncing quota usage status in the system

--root-ca-file=""
    If set, this root certificate authority will be included in service account's token secret. This must be a valid PEM-encoded CA bundle.

--route-reconciliation-period=0
    The period for reconciling routes created for Nodes by cloud provider.

--secondary-node-eviction-rate=0.01
    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.

--service-account-private-key-file=""
    Filename containing a PEM-encoded private RSA or ECDSA key used to sign service account tokens.

--service-cluster-ip-range=""
    CIDR Range for Services in cluster.

--service-sync-period=0
    The period for syncing services with their external load balancers

--terminated-pod-gc-threshold=12500
    Number of terminated pods that can exist before the terminated pod garbage collector starts deleting terminated pods. If <= 0, the terminated pod garbage collector is disabled.

--unhealthy-zone-threshold=0.55
    Fraction of Nodes in a zone which needs to be not Ready (minimum 3) for zone to be treated as unhealthy.

--use-service-account-credentials=false
    If true, use individual service account credentials for each controller.

OPTIONS INHERITED FROM PARENT COMMANDS

--azure-container-registry-config=""
    Path to the file container Azure container registry configuration information.

--google-json-key=""
    The Google Cloud Platform Service Account JSON Key to use for authentication.

--log-flush-frequency=0
    Maximum number of seconds between log flushes

SEE ALSO

openshift-start-kubernetes(1),

HISTORY

June 2016, Ported from the Kubernetes man-doc generator