Skip to content
All releases

okctl is out: clusters, deploys and logs from your terminal

Release 08 Jul 9 to 15

The dashboard is good, but some of us live in a terminal. okctl, the Ownkube command line, is out: sign in from your browser, then read your clusters, deployments and logs without leaving the shell, or connect your own AWS account from it. Each app also gained an auto-deploy switch.

okctl login, and your clusters are in the shell

Sign in from your browser, then inspect clusters, deployments, logs and connection details without leaving the terminal. Every read command prints JSON with -o json, so scripts and coding agents can use it too.

Run okctl login and a browser tab opens for you to sign in and pick an organization; the terminal picks up the session when you return. okctl status shows who you are signed in as, and okctl logout clears the session.

Every read command prints a table by default and structured data with -o json or -o yaml.

$ okctl login
CLI docs

Connect your AWS account without leaving the shell

okctl aws connect runs the connect flow for your own AWS account from the command line. With --deploy it creates the access stack using the AWS credentials already in your shell, which never reach Ownkube.

okctl aws list prints every connected account and its status, okctl aws verify <account-id> rechecks the role after a stack change, and okctl aws reconnect <account-id> re-arms an account whose stack was deleted.

$ okctl aws connect --deploy
Connect AWS docs

Pause deploys on push for one app

A switch next to the tracked branch on an app's Overview tab turns deploys on push on or off. It doesn't change the branch or create a revision.

More in this release

  • Tell okctl which organization you mean. If you belong to more than one organization, pass `--organization` or set `OKCTL_ORGANIZATION` and commands know which one to use instead of failing.
  • An expired session says so, and sessions last 90 days. `okctl login` and `okctl status` report an invalid or expired key as a sign-in problem instead of a server error. New CLI sessions last 90 days instead of 30.
  • A failed AWS connection says what to do next. It shows a plain title and a next step wherever you see it, instead of a raw CloudFormation status code.
  • The connect dialog closes itself. Once your AWS account reports back, the connect dialog confirms success and closes.
  • Switch organizations without leaving Settings. The organization name at the top of Settings is a switcher, so you can change organizations in place and stay on the tab you are on.
  • Long image names fit the Container card. A long image reference or commit tag no longer overflows the Container card on the Overview tab. Hover to see the full value.

Deploy your first app in five minutes.

Push a repo and get a live URL, with no cloud account or config.

$5 of signup credit.