create
******


Description
===========

Create a new cluster.


Usage
=====

   oci ce cluster create [OPTIONS]


Options
=======


--name [text]
-------------

The name of the cluster. Avoid entering confidential information.
[required]


--compartment-id, -c [text]
---------------------------

The OCID of the compartment in which to create the cluster. [required]


--vcn-id [text]
---------------

The OCID of the virtual cloud network (VCN) in which to create the
cluster. [required]


--kubernetes-version [text]
---------------------------

The version of Kubernetes to install into the cluster masters.
[required]


--wait-for-state [ACCEPTED|IN_PROGRESS|FAILED|SUCCEEDED|CANCELING|CANCELED]
---------------------------------------------------------------------------

This operation asynchronously creates, modifies or deletes a resource
and uses a work request to track the progress of the operation.
Specify this option to perform the action and then wait until the work
request reaches a certain state. If timeout is reached, a return code
of 2 is returned. For any other error, a return code of 1 is returned.


--max-wait-seconds [integer]
----------------------------

The maximum time to wait for the work request to reach the state
defined by --wait-for-state. Defaults to 1200 seconds.


--wait-interval-seconds [integer]
---------------------------------

Check every --wait-interval-seconds to see whether the work request to
see if it has reached the state defined by --wait-for-state. Defaults
to 30 seconds.


--service-lb-subnet-ids [complex type]
--------------------------------------

The two subnets configured to host load balancers in a Kubernetes
cluster. This is a complex type whose value must be valid JSON. The
value can be provided as a string on the command line or passed in as
a file using the file://path/to/file syntax.

The --generate-param-json-input option can be used to generate an
example of the JSON which must be provided. We recommend storing this
example in a file, modifying it as needed and then passing it back in
via the file:// syntax.


--dashboard-enabled [boolean]
-----------------------------

Select if you want to use the Kubernetes Dashboard to deploy and
troubleshoot containerized applications, and to manage Kubernetes
resources. Default value is true.


--tiller-enabled [boolean]
--------------------------

Select if you want Tiller (the server portion of Helm) to run in the
Kubernetes cluster. Default value is true.


--pods-cidr [text]
------------------

The available group of network addresses that can be allocated to pods
running in the cluster, expressed as a single, contiguous IPv4 CIDR
block. For example, 10.244.0.0/16.


--services-cidr [text]
----------------------

The available group of network addresses that can be exposed as
Kubernetes services (ClusterIPs), expressed as a single, contiguous
IPv4 CIDR block. For example, 10.96.0.0/16.


--from-json [text]
------------------

Provide input to this command as a JSON document from a file using the
file://path-to/file syntax.

The --generate-full-command-json-input option can be used to generate
a sample json file to be used with this command option. The key names
are pre-populated and match the command option names (converted to
camelCase format, e.g. compartment-id --> compartmentId), while the
values of the keys need to be populated by the user before using the
sample file as an input to this command. For any command option that
accepts multiple values, the value of the key can be a JSON array.

Options can still be provided on the command line. If an option exists
in both the JSON document and the command line then the command line
specified value will be used.

For examples on usage of this option, please see our "using CLI with
advanced JSON options" link: https://docs.cloud.oracle.com/iaas/Conte
nt/API/SDKDocs/cliusing.htm#AdvancedJSONOptions


-?, -h, --help
--------------

For detailed help on any of these individual commands, enter <command>
--help.
