Create the Kubeconfig YAML for a cluster.


oci ce cluster create-kubeconfig [OPTIONS]

Required Parameters

--cluster-id [text]

The OCID of the cluster.

Optional Parameters

--expiration [integer]

Deprecated. This field is no longer used.

--file [path]

The name of the file that will be updated with response data, or ‘-‘ to write to STDOUT. [default: ~/.kube/config]

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

--kube-endpoint [text]

The endpoint to target. A cluster may have multiple endpoints exposed but the kubeconfig can only target one at a time. Supported values LEGACY_KUBERNETES, PUBLIC_ENDPOINT, PRIVATE_ENDPOINT, VCN_HOSTNAME

Accepted values are:


Overwrites the contents of kubeconfig file specified using –file option or kubeconfig file at default location if –file is not used.

--token-version [text]

The version of the kubeconfig token. Supported value 2.0.0

--token-version [text]

The version of the kubeconfig token. Supported value is 2.0.0

Accepted values are:


Example using required parameter

Copy the following CLI commands into a file named Run the command by typing “bash” and replacing the example parameters with your own.

Please note this sample will only work in the POSIX-compliant bash-like shell. You need to set up the OCI configuration and appropriate security policies before trying the examples.

    export compartment_id=<substitute-value-of-compartment_id> #
    export kubernetes_version=<substitute-value-of-kubernetes_version> #
    export name=<substitute-value-of-name> #
    export vcn_id=<substitute-value-of-vcn_id> #

    cluster_id=$(oci ce cluster create --compartment-id $compartment_id --kubernetes-version $kubernetes_version --name $name --vcn-id $vcn_id --query --raw-output)

    oci ce cluster create-kubeconfig --cluster-id $cluster_id