spinframework / spinframework/spin-operator

Guided SpinKube install mission in KubeStellar Console

Open
#482 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
289
Forks
34
PR merge metrics
No merged PRs in 30d

Description

We built a guided install mission for SpinKube inside KubeStellar Console, a standalone Kubernetes dashboard (unrelated to legacy kubestellar/kubestellar, kubeflex, or OCM — zero shared code).

Open the SpinKube install mission

What the mission does

The mission runs against your live cluster via kubeconfig. Each step:

  1. Pre-flight — checks prerequisites (cert-manager, Helm, containerd-shim-spin runtime via Kwasm)
  2. Commands — shows the exact helm install / kubectl apply with flags explained. Copy-paste or run directly from the console
  3. Validation — after each step, queries the cluster to verify success (CRD registration, RuntimeClass, operator pod status)
  4. Troubleshooting — on failure, reads pod logs, events, and resource status from your cluster and suggests fixes
  5. Rollback — each step includes the corresponding helm uninstall / kubectl delete to undo

Works as read-only documentation too — no cluster connection required to browse.

Architecture
graph LR
    A["KubeStellar Console"] --> B["30+ Dashboards<br/>150+ Monitoring Cards"]
    A --> M["Marketplace<br/>(console-marketplace)"]
    A --> D["AI Mission Explorer"]
    D --> E["console-kb"]
    E --> F["186 Install Missions<br/>67 Solution Missions"]
    A --> C["AI Recommendations"]
    A --> H["kc-agent → Codex, Copilot,<br/>Claude CLI, Kube API, MCP"]
    click A href "https://console.kubestellar.io?utm_source=github&utm_medium=issue&utm_campaign=cncf_outreach&utm_term=spinkube" _blank
    click M href "https://github.com/kubestellar/console-marketplace?utm_source=github&utm_medium=issue&utm_campaign=cncf_outreach&utm_term=spinkube" _blank
    click E href "https://github.com/kubestellar/console-kb/blob/master/fixes/cncf-install/install-spinkube.json?utm_source=github&utm_medium=issue&utm_campaign=cncf_outreach&utm_term=spinkube" _blank
    click F href "https://console.kubestellar.io/missions/install-spinkube?utm_source=github&utm_medium=issue&utm_campaign=cncf_outreach&utm_term=spinkube" _blank
    click H href "https://github.com/kubestellar/console/tree/main/cmd/kc-agent?utm_source=github&utm_medium=issue&utm_campaign=cncf_outreach&utm_term=spinkube" _blank
  • console-kb — YAML-based knowledge base defining each mission's steps, commands, and validation checks (SpinKube installer definition)
  • console-marketplace — community-contributed monitoring cards per CNCF project (github.com/kubestellar/console-marketplace)
  • kc-agent — bridges coding agents (Codex, Copilot, Claude CLI) to Kube API and MCP servers (kubestellar-ops, kubestellar-deploy) for automated cluster operations
Install

Local (connects to your current kubeconfig context):

curl -sSL https://raw.githubusercontent.com/kubestellar/console/main/start.sh | bash

With GitHub OAuth:

export GITHUB_CLIENT_ID=<your-client-id>
export GITHUB_CLIENT_SECRET=<your-client-secret>
curl -sSL https://raw.githubusercontent.com/kubestellar/console/main/start.sh | bash

Deploy into a cluster:

curl -sSL https://raw.githubusercontent.com/kubestellar/console/main/deploy.sh | bash

Mission definitions are open source — PRs to improve the SpinKube mission welcome at install-spinkube.json. Feel free to close if not relevant.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading console-kb/fixes/cncf-install/install-spinkube.json, the linked SpinKube mission definition, and the KubeStellar Console mission page. The issue does not specify a concrete change or acceptance criteria; a contributor would need clarification before knowing what an improved mission should contain.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm, kubernetes, wasm
Domain
devops, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.