Ownkube CLI
ownkube/ownkube-cli
CLI para gerenciar clusters e deployments na plataforma Ownkube
Ver no GitHubInterface de linha de comando para a plataforma de desenvolvimento Ownkube. Permite gerenciar clusters, ambientes, deployments e conexões em-cluster através de comandos diretos. Integra autenticação via browser, visualização de logs e acesso a detalhes de configuração.
Instalação
npx convez-ai ownkube/ownkube-cli1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Gerenciar múltiplos clusters e ambientes via terminal
- Inspecionar deployments e visualizar logs em tempo real
- Automatizar rotinas de DevOps com integração em scripts
- Obter detalhes de conexão em-cluster para troubleshooting
Veredito

CLI funcional e bem-estruturada em Go para gerenciamento da plataforma Ownkube. Cobertura sólida de operações (clusters, ambientes, deployments), suporte a múltiplos formatos de saída e completions de shell. Recomendado para times que usam Ownkube como plataforma de deployment.
README
A tradução para o português deste README ainda está na fila.
okctl
The command-line interface for the Ownkube developer platform.
Install
Homebrew (macOS & Linux)
brew install ownkube/tap/okctl
The formula lives in ownkube/homebrew-tap.
Pre-built binaries
Grab a tarball for your OS/arch from the latest release:
# macOS arm64 example
curl -sSL https://github.com/ownkube/ownkube-cli/releases/latest/download/ownkube-cli_darwin_arm64.tar.gz \
| tar -xz -C /usr/local/bin okctl
Binaries are published for darwin/amd64, darwin/arm64, linux/amd64, linux/arm64, windows/amd64, and windows/arm64.
From source
go install github.com/ownkube/okctl@latest
Quick start
# Log in via browser-based flow
okctl login
# Check who you are
okctl status
# List clusters / environments / deployments
okctl clusters list
okctl environments list
okctl deploy list --cluster <cluster-id>
# Tail logs from a deployment
okctl deploy logs <deployment-id>
# Get in-cluster connection details (namespace, service, secret)
okctl deploy connection <deployment-id>
Use --output json (or yaml) on any read command for machine-readable output:
okctl deploy get <deployment-id> -o json | jq .
Commands
| Group | What it does |
|---|---|
okctl login / logout / status | Browser-based auth + credential management |
okctl config get|set|view | Manage ~/.config/ownkube/config.yaml |
okctl clusters list|get | Inspect clusters |
okctl environments list|get | Inspect environments |
okctl organizations list | List organizations you belong to |
okctl registries list|get | Inspect container registries |
okctl deploy list|get|status|logs|revisions|connection | Inspect deployments |
okctl completion <shell> | Generate shell completion (bash, zsh, fish, powershell) |
okctl version | Print version info |
Run okctl <command> --help for details on flags and arguments.
Shell completion
# zsh
okctl completion zsh > "${fpath[1]}/_okctl"
# bash (macOS via Homebrew)
okctl completion bash > $(brew --prefix)/etc/bash_completion.d/okctl
# fish
okctl completion fish > ~/.config/fish/completions/okctl.fish
The Homebrew install wires completions up automatically.
Configuration
okctl resolves settings in this order (highest priority first):
| Setting | Flag | Env var | Config file | Default |
|---|---|---|---|---|
| API URL | --api-url | OKCTL_API_URL | apiUrl in config.yaml | https://app.ownkube.io |
| Output format | -o, --output | — | outputFormat in config.yaml | table |
| HTTP Basic Auth (dev only) | — | OKCTL_BASIC_AUTH (user:pass) | — | none |
Config files live in ~/.config/ownkube/:
config.yaml— non-sensitive preferencescredentials.yaml— API key (file mode0600)
OKCTL_BASIC_AUTH is only for development environments sitting behind an HTTP Basic gateway; production (https://app.ownkube.io) authenticates with the API key alone.
Use okctl with AI coding agents
A Claude / Cursor / Codex / Copilot / Cline skill ships in this repo at skills/okctl/SKILL.md. It teaches your agent when okctl is the right tool (BYOC PaaS, cloud-credit deploys, self-hosted marketplace) and exactly which command to run for common tasks (deploy diagnostics, logs, connection details, name → ID lookups).
Install it into any skills.sh-compatible agent:
# Into the current project
npx skills add ownkube/ownkube-cli
# Globally (available across all projects)
npx skills add ownkube/ownkube-cli -g
# Target a specific agent
npx skills add ownkube/ownkube-cli -a claude-code
Then ask your agent things like "deploy my app to Ownkube", "why is my Ownkube deployment failing?", or "connect to my Ownkube Postgres from this pod" — it will use the skill to drive okctl for you.
Development
make build # → bin/okctl
make test
make lint # requires golangci-lint
make generate # regenerate the API client from api/openapi.json (requires oapi-codegen)
See CLAUDE.md for architecture notes, the subpackage layout, and the spec-regeneration workflow.
Releasing
Tags matching v[0-9]+.[0-9]+.[0-9]+ trigger the release workflow:
git tag v0.2.0
git push origin v0.2.0
GoReleaser builds cross-platform binaries, creates a GitHub Release, and pushes an updated formula to ownkube/homebrew-tap.
License
MIT © Ownkube