openshift-start-master man page

openshift start master — Launch a master

Synopsis

openshift start master [Options]

Description

Start a master server

This command helps you launch a master server. Running

openshift start master

will start a master listening on all interfaces, launch an etcd server to store persistent data, and launch the Kubernetes system components. The server will run in the foreground until you terminate the process.

Note: starting the master without passing the --master address will attempt to find the IP address that will be visible inside running Docker containers. This is not always successful, so if you have problems tell the master what public address it should use via --master=<ip>.

You may also pass --etcd=<address> to connect to an external etcd server.

You may also pass --kubeconfig=<path> to connect to an external Kubernetes cluster.

Options

--certificate-authority=[]
Optional files containing signing authorities to use (in addition to the generated signer) to verify the API server's serving certificate.
--config=""
Location of the master configuration file to run from. When running from a configuration file, all other command-line arguments are ignored.
--cors-allowed-origins=[]
List of allowed origins for CORS, comma separated. An allowed origin can be a regular expression to support subdomain matching. CORS is enabled for localhost, 127.0.0.1, and the asset server by default.
--create-certs=true
Indicates whether missing certs should be created
--dns="tcp://0.0.0.0:8053"
The address to listen for DNS requests on.
--etcd=" ⟨https://0.0.0.0:4001"⟩
The address of the etcd server (host, host:port, or URL). If specified, no built-in etcd will be started.
--etcd-dir="openshift.local.etcd"
The etcd data directory.
--host-subnet-length=9
The length of subnet each host is given from the network-cidr.
--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).
--master=" ⟨https://localhost:8443"⟩
The master address for use by OpenShift components (host, host:port, or URL). Scheme and port default to the --listen scheme and port. When unset, attempt to use the first public IPv4 non-loopback address registered on this host.
--network-cidr="10.128.0.0/14"
The CIDR string representing the network that all containers should belong to.
--network-plugin=""
The name of the networking plugin to be used for networking.
--pause=false
If true, wait for a signal before starting the controllers.
--portal-net="172.30.0.0/16"
The CIDR string representing the network that portal/service IPs will be assigned from. This must not overlap with any IP ranges assigned to nodes for pods.
--public-master=" ⟨https://localhost:8443"⟩
The master address for use by public clients, if different (host, host:port, or URL). Defaults to same as --master.
--write-config=""
Directory to write an initial config into. After writing, exit without starting the server.

Options Inherited from Parent Commands

--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), openshift-start-master-api(1), openshift-start-master-controllers(1),

History

June 2016, Ported from the Kubernetes man-doc generator

Referenced By

openshift-start(1), openshift-start-master-api(1), openshift-start-master-controllers(1).

Openshift CLI User Manuals Openshift June 2016