oc-cluster man page

oc cluster — Start and stop OpenShift cluster


oc cluster [OPTIONS]


Manage a local OpenShift cluster.

The OpenShift cluster will run as an all-in-one container on a Docker host. The Docker host may be a local VM (ie. using docker-machine on OS X and Windows clients), remote machine, or the local Unix host.

To use an existing Docker connection, ensure that Docker commands are working and that you can create new containers. For OS X and Windows clients, a docker-machine with the VirtualBox driver can be created for you using the --create-machine option.

By default, etcd data will not be preserved between container restarts. If you wish to preserve your data, specify a value for --host-data-dir and the --use-existing-config flag.

Default routes are setup using xip.io and the host ip of your cluster. To use a different routing suffix, use the --routing-suffix flag.

Options Inherited from Parent Commands

DEPRECATED: The API version to use when talking to the server

Username to impersonate for the operation.

Path to a cert. file for the certificate authority.

Path to a client certificate file for TLS.

Path to a client key file for TLS.

The name of the kubeconfig cluster to use

Path to the config file to use for CLI requests.

The name of the kubeconfig context to use

The Google Cloud Platform Service Account JSON Key to use for authentication.

If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure.

Maximum number of seconds between log flushes

Require server version to match client version

-n, --namespace=""
If present, the namespace scope for this CLI request.

The address and port of the Kubernetes API server

Bearer token for authentication to the API server.

The name of the kubeconfig user to use

See Also

oc(1), oc-cluster-down(1), oc-cluster-up(1),


June 2016, Ported from the Kubernetes man-doc generator

Referenced By

oc(1), oc-cluster-down(1), oc-cluster-up(1).

Openshift CLI User Manuals Openshift June 2016