Home / Keptn v1 Docs / Release 0.19.x / Reference / Keptn CLI

Keptn CLI

Explains how to download and install the Keptn CLI as well as which commands are available.

Commands

Auto-generated documentation of keptn CLI

In this section, the functionality and commands of the Keptn CLI are described. The Keptn CLI allows installing, configuring, and uninstalling Keptn. Furthermore, the CLI allows creating projects, services, and sending new artifact events.

Automatic install of Keptn CLI

Note: This will work on Linux (and WSL2), as well as macOS. Windows users need bash, curl, and awk installed (e.g., using Git Bash).

Download the latest stable Keptn version from GitHub, unpack it and move it to /usr/local/bin/keptn.

curl -sL https://get.keptn.sh | bash

Verify that the installation has worked and that the version is correct by running:
```
keptn version
```
or if you are on Windows
```
.\keptn.exe version
```

Installation on macOS using brew

The following command will automatically fetch the latest Keptn CLI via Homebrew

brew install keptn

Verify that the installation has worked and that the version is correct by running:

keptn version

Updating

brew upgrade keptn

Uninstall

brew uninstall keptn

Download and manual install of Keptn CLI

Every release of Keptn provides binaries for the Keptn CLI. These binaries are available for Linux, macOS, and Windows.

Download the version matching your operating system
Unpack the download
Find the keptn binary in the unpacked directory.

Linux / macOS: Add executable permissions (chmod +x keptn), and move it to the desired destination (e.g. mv keptn /usr/local/bin/keptn)
Windows: move/copy the executable to the desired folder and, optionally, add the executable to the PATH environment variable for a more convenient experience.

Verify that the installation has worked and that the version is correct by running:

keptn version

Start using Keptn CLI

In the following, the commands provided by the Keptn CLI are described. To list all available commands just execute:

keptn --help

All of these commands also support the help flag (--help), which describes details of the respective command (e.g., usage of the command or description of flags).

Authenticate Keptn CLI

To authenticate the Keptn CLI against the Keptn cluster, the exposed Keptn endpoint and API token are required.

Get the Keptn endpoint from the api-gateway-nginx. (If you are using port-forward to expose Keptn, your endpoint is localhost and the port you forwarded Keptn to, e.g.: http://localhost:8080)

kubectl -n keptn get service api-gateway-nginx


```console
NAME                TYPE        CLUSTER-IP    EXTERNAL-IP                  PORT(S)   AGE
api-gateway-nginx   ClusterIP   10.117.0.20   <ENDPOINT_OF_API_GATEWAY>    80/TCP    44m

Set the environment variable KEPTN_ENDPOINT:

KEPTN_ENDPOINT=<ENDPOINT_OF_API_GATEWAY>

Set the environment variable KEPTN_API_TOKEN:

KEPTN_API_TOKEN=$(kubectl get secret keptn-api-token -n keptn -ojsonpath={.data.keptn-api-token} | base64 --decode)

To authenticate the CLI against the Keptn cluster, use the keptn auth command:

keptn auth --endpoint=$KEPTN_ENDPOINT --api-token=$KEPTN_API_TOKEN

Note: If you receive a warning Using a file-based storage for the key because the password-store seems to be not set up. this is because a password store could not be found in your environment. In this case, the credentials are stored in ~/.keptn/.password-store in your home directory.

Please expand the corresponding section matching your CLI tool:

For the Windows PowerShell, a small script is provided that installs the PSYaml module and sets the environment variables.

Set the environment variable KEPTN_ENDPOINT:

$Env:KEPTN_ENDPOINT = '<ENDPOINT_OF_API_GATEWAY>'

Copy the following snippet and paste it in the PowerShell. The snippet retrieves the API token and sets the environment variable KEPTN_API_TOKEN:

$tokenEncoded = $(kubectl get secret keptn-api-token -n keptn -ojsonpath='{.data.keptn-api-token}')
$Env:KEPTN_API_TOKEN = [System.Text.Encoding]::UTF8.GetString([System.Convert]::FromBase64String($tokenEncoded))

To authenticate the CLI against the Keptn cluster, use the keptn auth command:

keptn auth --endpoint=$Env:KEPTN_ENDPOINT --api-token=$Env:KEPTN_API_TOKEN

In the Windows Command Line, a couple of steps are necessary.

Set the environment variable KEPTN_ENDPOINT:

set KEPTN_ENDPOINT=<ENDPOINT_OF_API_GATEWAY>

Get the Keptn API Token encoded in base64:

kubectl get secret keptn-api-token -n keptn -ojsonpath={.data.keptn-api-token}

abcdefghijkladfaea

Take the encoded API token - it is the value from the key keptn-api-token (in this example, it is abcdefghijkladfaea) and save it in a text file, e.g., keptn-api-token-base64.txt
Decode the file:

certutil -decode keptn-api-token-base64.txt keptn-api-token.txt

Open the newly created file keptn-api-token.txt, copy the value and paste it into the next command:

set KEPTN_API_TOKEN=keptn-api-token

To authenticate the CLI against the Keptn cluster, use the keptn auth command:

keptn.exe auth --endpoint=%KEPTN_ENDPOINT% --api-token=%KEPTN_API_TOKEN%

Use Keptn CLI with multiple contexts

After authenticating the Keptn CLI with multiple Kubernetes clusters, we can directly run Keptn CLI commands in the current context.

As soon as you switch the Kube context (e.g., by executing: kubectl config use-context my-cluster-name), the Keptn CLI will detect the change of the Kube context and ask you to run the command in the changed context or not.
If the Keptn CLI is authenticated for that particular context, the command will run successfully; else it will end up throwing the error: This command requires to be authenticated. See "keptn auth" for details"
In case of multi-installation of Keptn in the same cluster, we need to pass the flag --namespace or -n to tell the Keptn CLI to use the credentials for that particular Keptn installation, else it will take the default namespace which is: keptn

Use Keptn CLI with KEPTNCONFIG

The KEPTNCONFIG environment variable holds a config file that contains the credentials (i.e. API_TOKEN and ENDPOINT) for the Keptn installation.

The KEPTNCONFIG file format:

contexts:     
- api_token: abcdxxxxxxxx1234
  endpoint: https://localhost:8080/api
  name: keptn-test                  # context name                    
  namespace: keptn-test             # namespace name, the default is `keptn` if not set
- api_token: abcdxxxxxxxx1234
  endpoint: https://91.xxx.xxx.xxx.nip.io/api
  name: keptn-demo

If KEPTNCONFIG environment variable is defined, the Keptn CLI reads the credentials from it.
If the credentials are not found in the config file, it will fall back to the credential manager.

Enabling shell autocompletion of Keptn CLI

Keptn CLI provides autocompletion support for Bash and Zsh, which can save you a lot of typing.

Below are the procedures to set up autocompletion for Bash and Zsh. Please expand the corresponding section matching your configuration.

The Keptn CLI completion script for Bash can be generated with the command keptn completion bash. Sourcing the completion script in your shell enables Keptn CLI autocompletion.

However, the completion script depends on bash-completion, which means that you have to install this software first (you can test if you have bash-completion already installed by running type _init_completion).

Install bash-completion for Linux

bash-completion is provided by many package managers (see here). You can install it with apt-get install bash-completion or yum install bash-completion, etc.

The above commands create /usr/share/bash-completion/bash_completion, which is the main script of bash-completion. Depending on your package manager, you have to manually source this file in your ~/.bashrc file.

To find out, reload your shell and run type _init_completion. If the command succeeds, you’re already set, otherwise add the following to your ~/.bashrc file:

source /usr/share/bash-completion/bash_completion

Reload your shell and verify that bash-completion is correctly installed by typing type _init_completion.

Enable Keptn CLI autocompletion for linux (bash)

You now need to ensure that the Keptn CLI completion script gets sourced in all your shell sessions. There are two ways in which you can do this:

source the completion script in your ~/.bashrc file:

echo 'source <(keptn completion bash)' >>~/.bashrc

Add the completion script to the /etc/bash_completion.d directory:

keptn completion bash >/etc/bash_completion.d/keptn

If you have an alias for Keptn CLI, you can extend shell completion to work with that alias:

echo 'alias kc=keptn' >>~/.bashrc
echo 'complete -F __start_keptn kc' >>~/.bashrc

After reloading your shell, Keptn CLI autocompletion will be enabled successfully.

The Keptn CLI completion script for Bash can be generated with keptn completion bash. Sourcing this script in your shell enables Keptn CLI autocompletion.

However, the Keptn CLI autocompletion script depends on bash-completion which you thus have to previously install.

Warning: There are two versions of bash-completion, v1 and v2. V1 is for Bash 3.2 (which is the default on macOS), and v2 is for Bash 4.1+. The Keptn CLI autocompletion script doesn’t work correctly with bash-completion v1 and Bash 3.2. It requires bash-completion v2 and Bash 4.1+. Thus, to be able to correctly use the Keptn CLI autocompletion on macOS, you have to install and use Bash 4.1+ (instructions). The following instructions assume that you use Bash 4.1+ (that is, any Bash version of 4.1 or newer).

Install bash-completion for macOS

Note: As mentioned, these instructions assume you use Bash 4.1+, which means you will install bash-completion v2 (in contrast to Bash 3.2 and bash-completion v1, in which case Keptn CLI completion won’t work).

You can test if you have bash-completion v2 already installed with type _init_completion. If not, you can install it with Homebrew:

brew install bash-completion@2

As stated in the output of this command, add the following to your ~/.bash_profile file:

export BASH_COMPLETION_COMPAT_DIR="/usr/local/etc/bash_completion.d"
[[ -r "/usr/local/etc/profile.d/bash_completion.sh" ]] && . "/usr/local/etc/profile.d/bash_completion.sh"

Reload your shell and verify that bash-completion v2 is correctly installed with type _init_completion.

Enable autocompletion for macOS (bash)

You now have to ensure that the Keptn CLI completion script gets sourced in all your shell sessions. There are multiple ways to achieve this:

Source the completion script in your ~/.bash_profile file:

echo 'source <(keptn completion bash)' >>~/.bash_profile

Add the completion script to the /usr/local/etc/bash_completion.d directory:

keptn completion bash >/usr/local/etc/bash_completion.d/keptn

If you have an alias for Keptn CLI, you can extend shell completion to work with that alias:

echo 'alias kc=keptn' >>~/.bash_profile
echo 'complete -F keptn kc' >>~/.bash_profile

After reloading your shell, Keptn CLI autocompletion will be enabled successfully.

The Keptn CLI completion script for Zsh can be generated with the command keptn completion zsh. Sourcing the completion script in your shell enables Keptn CLI autocompletion.

To do so in all your shell sessions, add the following to your ~/.zshrc file:

source <(keptn CLI completion zsh)

Set the keptn completion code for zsh to autoload on startup by executing the following:

keptn completion zsh > "${fpath[1]}/_keptn

If you have an alias for Keptn CLI, you can extend shell completion to work with it as follows:

echo 'alias kc=keptn' >>~/.zshrc
echo 'complete -F __start_keptn kc' >>~/.zshrc

After reloading your shell, Keptn CLI autocompletion will be enabled successfully.

If you encounter an error similar to complete:13: command not found: compdef, then add the following to the beginning of your ~/.zshrc file:

autoload -Uz compinit
compinit

Using an HTTP Proxy

To make the CLI access Keptn via an HTTP proxy, you can make use of the environment variables HTTP_PROXY and HTTPS_PROXY. If these are set, all requests sent by the CLI will go through the specified URL. The following examples illustrate how these variables can be set on the platforms supported by the CLI:

Linux or macOS

$ export HTTP_PROXY=http://10.0.0.1:8888
$ export HTTP_PROXY=http://my-proxy.example.com:8888
$ export HTTPS_PROXY=http://10.0.0.1:8888
$ export HTTPS_PROXY=http://my-proxy.example.com:8888
$ export HTTP_PROXY=http://username:password@my-proxy.example.com:8888 # with basic HTTP authentication
$ export HTTPS_PROXY=http://username:password@my-proxy.example.com:8888 # with basic HTTP authentication

Windows

C:\> setx HTTP_PROXY=http://10.0.0.1:8888
C:\> setx HTTP_PROXY=http://my-proxy.example.com:8888
C:\> setx HTTPS_PROXY=http://10.0.0.1:8888
C:\> setx HTTPS_PROXY=http://my-proxy.example.com:8888
C:\> setx HTTP_PROXY=http://username:password@my-proxy.example.com:8888 # with basic HTTP authentication
C:\> setx HTTPS_PROXY=http://username:password@my-proxy.example.com:8888 # with basic HTTP authentication