openshift-start-node man page

openshift start node — Launch a node

Synopsis

openshift start node [Options]

Description

Start a node

This command helps you launch a node.  Running

openshift start node --config=<node-config>

will start a node with given configuration file. The node will run in the foreground until you terminate the process.

Options

--bootstrap=false

Use the provided .kubeconfig file to perform initial node setup (experimental).

--config=""

Location of the node configuration file to run from. When running from a configuration file, all other command-line arguments are ignored.

--disable=""

The set of node components to disable

--enable="dns,kubelet,plugins,proxy"

The set of node components to enable

--expire-days=730

Validity of the certificates in days (defaults to 2 years). WARNING: extending this above default value is highly discouraged.

--hostname="<hostname>"

The hostname to identify this node with the master.

--images="openshift/origin-${component}:${version}"

When fetching images used by the cluster for important components, use this format on both master and nodes. The latest release will be used by default.

--kubeconfig=""

Path to the kubeconfig file to use for requests to the Kubernetes API.

--kubernetes=" ⟨https://localhost:8443"⟩

removed in favor of --kubeconfig

--latest-images=false

If true, attempt to use the latest images for the cluster instead of the latest release.

--listen=" ⟨https://0.0.0.0:8443"⟩

The address to listen for connections on (scheme://host:port).

--network-plugin=""

The network plugin to be called for configuring networking for pods.

--recursive-resolv-conf=""

An optional upstream resolv.conf that will override the DNS config.

--volume-dir="openshift.local.volumes"

The volume storage directory.

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(1),

History

June 2016, Ported from the Kubernetes man-doc generator

Referenced By

openshift-start(1).

Openshift CLI User Manuals June 2016