GraphCanon updated 3w · GitHub synced 3w
Decision brief
Console is a fully integrated automated Kubernetes management tool with paths for hosted demo access and self-hosted local installation.
Good fit when
- Need to evaluate console features without setup of your own clusters
- Looking for a quick way to start managing your own data locally
Avoid when
- Seeking direct interaction with your local Kubernetes agent at first glance
- Preferring immediate integration and management in an existing non-Kubernetes environment
Observed Jul 16, 2026 · Source: enrich:decision_facts
Verify the decision
Adoption
Package downloads where a registry match exists. GitHub stars (125) are secondary evidence.
- npm downloads (30d)
- 235,304·npm downloads API·3w
Maintenance and security
Full trust report- Maintenance
- Very active (0d since push)
- As of 3w
- Provenance
- Not a fork · Organization account
- As of 3w
- Security (OSV)
- No criticals
- As of 1mo
Public GitHub metadata and optional OSV scans. Signals, not a guarantee. Trust methodology.
Install
npm install console npmSimilar tools
Same-category neighbours. No typed graph edges are catalogued for this tool yet.
Evidence and technical details
Sourced facts, taxonomy, compatibility claims, README excerpt, and machine-readable endpoints.
Overview
A fully integrated automated Kubernetes management tool with options for hosted demo access and self-hosted installation.
Capability facts
- Deploy
- Self-host
Source: dockerfile:Dockerfile · Aug 2, 2026
- Docker
- Dockerfile present
Source: dockerfile:Dockerfile · Aug 2, 2026
- Languages
- typescript
Source: github.language · Aug 2, 2026
Categories
Tags
README
Try it now (no install)
The fastest way to evaluate the console is the hosted version — no Kubernetes cluster, no install, no configuration. Demo data is built in:
The hosted demo is a self-contained showcase: it serves canned demo data and intentionally does not talk to a local agent (LOCAL_AGENT_HTTP_URL is disabled in the Netlify build, so the browser cannot reach a kc-agent on your laptop). Use it to explore the UI, browse missions, and test cards without touching your machine. To work against your own clusters or use AI features with your own keys, you need to self-host the console — see the next section.
Local install (self-host)
The quickest path to a working console with your own data. start.sh downloads the pre-built console binary and a pre-built kc-agent, starts both, and opens http://localhost:8080:
curl -sSL https://raw.githubusercontent.com/kubestellar/console/main/start.sh | bash
Deploy into a cluster instead with deploy.sh (--openshift, --ingress <host>, --github-oauth, --uninstall). See docs/deploy.md for the full flag, environment-variable, exit-code, and example reference. For Helm chart installs that should talk to an in-cluster Kagenti backend, see Connecting Kagenti and the Kagenti deployment guide for controller/agent topology, setup steps, and troubleshooting.
Same install command as macOS / Linux
curl -sSL https://raw.githubusercontent.com/kubestellar/console/main/start.sh | bash
> **⚠️ Windows PowerShell `curl` gotcha:** In PowerShell, `curl` is an alias
> for `Invoke-WebRequest`, which behaves completely differently from the real
> curl. If you need to test endpoints from PowerShell (outside WSL), always
> use **`curl.exe`** instead of `curl`, or use the native PowerShell cmdlet:
>
> ```powershell
> # Option 1 — use curl.exe (the real curl shipped with Windows 10+)
> curl.exe -s http://localhost:8080/health
>
> # Option 2 — use PowerShell native cmdlet
> Invoke-RestMethod http://localhost:8080/health
> ```
**Building `kc-agent` from source is a separate path** — only needed if you want a development build of the agent rather than the prebuilt binary that `start.sh` already installs. It requires Go **1.26.4+** (the version pinned in `go.mod`) and `git`. Ubuntu's `golang-go` package usually lags the current release; use the [official Go install](https://go.dev/doc/install) or the `longsleep/golang-backports` PPA to get a recent version:
```bash
---
# add-apt-repository lives in software-properties-common — install it
---
### In-Cluster Deployment
Configuration for running the console inside a Kubernetes cluster.
| Variable | Required | Default | Description |
|----------|----------|---------|-------------|
| `POD_NAMESPACE` | Optional | — | Kubernetes namespace where console pod runs (used for self-upgrade feature) |
---
## License
Apache License 2.0 — see [LICENSE](LICENSE).
For agents
This page has a .md twin and JSON over the API.