Version: 0.7

kore create cluster

kore create cluster#

Create a kubernetes cluster within the team


Provides the ability to provision a kubernetes cluster in the team. The cluster itself is provisioned from a predefined plan (a template). You can view the plans available to you via $ kore get plans. Once the cluster has been built the members of your team can gain access via running $ kore login.

kore create cluster [flags]


Note: you retrieve a list of all the plans available to you via:
$ kore get plans
$ kore get plans <name> -o yaml
$ kore -t <myteam> create cluster dev --plan gke-development --allocation <allocation_name>
$ kore -t <myteam> create cluster dev --plan gke-development -a <name> --cluster=app1,app2
Check the status of the cluster
$ kore -t <myteam> get cluster dev -o yaml
You can override the plan parameters using the --param (examples below)
$ kore -t <myteam> create cluster dev --param authProxyAllowedIPs.0=
$ kore -t <myteam> create cluster dev --param authProxyAllowedIPs='["","2,2,2,2"]'
$ kore -t <myteam> create cluster dev --param authProxyAllowedIPs.-1=
Alternatively you can use json directly
$ kore -t <myteam> create cluster dev --param nodeGroups.1'='{json}|[json]'
Note if you only have the one allocation for a given cloud provider in your
team you can forgo the the need to specify the credentials allocation
(-a|--allocation) as they will be automatically provisioned for you.
Now update your kubeconfig to use your team's provisioned cluster. This will
modify your ${HOME}/.kube/config. Now you can use 'kubectl' to interact with
your team's cluster.
$ kore kubeconfig -t <myteam>
By default all access to clusters is short-lived and users must assume a
set of permissions before working with clusters
$ kore assume --help


-a, --allocation NAME name of the allocated cloud account / org to use for this cluster NAME
-d, --description DESCRIPTION a short description for the cluster DESCRIPTION
--dry-run shows the resource but does not apply or create (defaults: false)
-h, --help help for cluster
--param KEY=VALUE a series of key value pairs used to override plan parameters KEY=VALUE
-p, --plan NAME plan which this cluster will be templated from NAME
-T, --show-time BOOL shows the time it took to successfully provision a new cluster BOOL

Options inherited from parent commands#

--debug indicates we should use debug / trace logging (defaults: false)
--force is used to force an operation to happen (defaults: false)
--no-wait indicates if we should wait for resources to provision
-o, --output string the output format of the resource (json,yaml,table,template) (default "table")
--profile string allows you to explicitly set the selected profile
--show-headers indicates we should display headers on table out (default true)
-t, --team string the team you are operating within
--verbose enables verbose logging for debugging purposes (defaults: false)