Guides / Get started

Sign in and get kubectl access

Every call to the API needs a token. Once you can sign in, get one for yourself and a kubeconfig to go with it. Scripts and pipelines should get their own token from a service account instead (see Automate with a service account).

Sign in with etorm login

The etorm command-line tool signs you in through your browser and creates a personal token. It then writes a kubeconfig with one context for the platform and one for each project you can reach. You build the tool from source.

cargo build --release -p etorm
./target/release/etorm login

The token lasts 30 days unless you pass --days N (1 to 365). The tool prints nothing secret. It writes the kubeconfig to ~/.config/etorm/kubeconfig with mode 0600, so point kubectl at that file and pick a context.

export KUBECONFIG=~/.config/etorm/kubeconfig
kubectl config get-contexts
kubectl --context acme-prod get vpcs

On a machine without a browser, run etorm login --no-browser and open the printed address on a computer whose browser can reach the machine's loopback port. If you cannot do that, get the kubeconfig from the console instead.

Or copy a kubeconfig from the console

Sign in at the console and open kubectl access in the activity bar (the terminal icon). Choose a lifetime and copy the kubeconfig. The console shows it once, so save it to a file straight away and use it as above.

See and revoke your tokens

List the tokens you hold and delete any you no longer trust.

kubectl --context etorm get apitokens        # your own tokens only
kubectl --context etorm delete apitoken <name>   # revokes at once
./target/release/etorm logout                     # revokes the login token and removes the files

A personal token has exactly your rights, in every project you can reach, and nothing more. You can hold at most 20.

What a token looks like

A token is a bearer secret of the form etorm.<cluster>.<name>.<secret>. Anyone who holds it can act as you. We keep only a hash of it on the server, so we cannot show you a lost token again. Create a new one and delete the old one. Never put a token in a URL, a commit or a log.

Next

Create a billing account and a project.