create
******


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

Create a new node pool.


Usage
=====

   oci ce node-pool create [OPTIONS]


Options
=======


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

The OCID of the compartment in which the node pool exists. [required]


--cluster-id [text]
-------------------

The OCID of the cluster to which this node pool is attached.
[required]


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

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


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

The version of Kubernetes to install on the nodes in the node pool.
[required]


--node-image-name [text]
------------------------

The name of the image running on the nodes in the node pool.
[required]


--node-shape [text]
-------------------

The name of the node shape of the nodes in the node pool. [required]


--subnet-ids [complex type]
---------------------------

The OCIDs of the subnets in which to place nodes for this node pool.
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.

   [required]


--node-metadata [complex type]
------------------------------

A list of key/value pairs to add to each underlying OCI instance in
the node pool. 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.


--initial-node-labels [complex type]
------------------------------------

A list of key/value pairs to add to nodes after they join the
Kubernetes cluster.

This option is a JSON list with items of type KeyValue.  For
documentation on KeyValue please see our API reference: https://docs.
cloud.oracle.com/api/#/en/containerengine/20180222/datatypes/KeyValue.
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.


--ssh-public-key [text]
-----------------------

The SSH public key to add to each node in the node pool.


--quantity-per-subnet [integer]
-------------------------------

The number of nodes to create in each subnet.


--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.


--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.
