Version: 0.7

kore local

kore local#

Provides the provision of local installation for Kore for testing

Synopsis#

Bootstrap provides an experimental means of bootstrapping a local Kore installation. At present the local installation uses "kind" https://github.com/kubernetes-sigs/kind.

Unless specified otherwise it will deploy an official tagged release from Github, though this can be overridden using the --release flag. Note the installation is performed via helm with a local ${HOME}/.kore/values.yaml generated in the directory. If you wish to change any of the values post installation, update the values.yaml file and re-run the 'up' command.

Note the data persistence is tied to the installation provider. For kind as long as the container is not delete the data is kept.

kore local [flags]

Examples#

# Provision a local kore instance called 'kore' (defaults to kind)
$ kore local up
# By default we will download the official tagged release; you can however override this
# behaviour by using the --release and --version flags. Note, its best to leave these unless
# you know explicitly know what you need to override.
$ kore local up --release ./charts/kore
$ kore local up --release https://URL
# Override the version
$ kore local up --version latest --release ./charts/kore
# Destroy the local installation
$ kore local destroy
# To stop the local installed without deleting the data
$ kore local stop
The application should be available on http://127.0.0.1:3000. You can provision the
CLI via.
$ kore login -a http://127.0.0.1:10080 local
Post the command your Kubectl context is switched to the kind installation:
$ kubectl config current-context

Options#

-h, --help help for local

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)

SEE ALSO#