networkservicemesh / networkservicemesh/api
Guided Network Service Mesh install mission in KubeStellar Console
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 18
- Forks
- 22
- Avg merge
- 27m
- Merged PRs (30d)
- 3
Description
We built a guided install mission for Network Service Mesh inside KubeStellar Console, a standalone Kubernetes dashboard (unrelated to legacy kubestellar/kubestellar, kubeflex, or OCM — zero shared code).
→ Open the Network Service Mesh install mission
What the mission does
The mission runs against your live cluster via kubeconfig. Each step:
- Pre-flight — checks prerequisites (namespace existence, RBAC permissions, required CRDs)
- Commands — shows the exact
helm install/kubectl applywith flags explained. Copy-paste or run directly from the console - Validation — after each step, queries the cluster to verify success (pod phase, CRD registration, service endpoints)
- Troubleshooting — on failure, reads pod logs, events, and resource status from your cluster and suggests fixes
- Rollback — each step includes the corresponding
helm uninstall/kubectl deleteto 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=network-service-mesh" _blank
click M href "https://github.com/kubestellar/console-marketplace?utm_source=github&utm_medium=issue&utm_campaign=cncf_outreach&utm_term=network-service-mesh" _blank
click E href "https://github.com/kubestellar/console-kb/blob/master/fixes/cncf-install/install-network-service-mesh.json?utm_source=github&utm_medium=issue&utm_campaign=cncf_outreach&utm_term=network-service-mesh" _blank
click F href "https://console.kubestellar.io/missions/install-network-service-mesh?utm_source=github&utm_medium=issue&utm_campaign=cncf_outreach&utm_term=network-service-mesh" _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=network-service-mesh" _blank
- console-kb — YAML-based knowledge base defining each mission's steps, commands, and validation checks (Network Service Mesh 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 Network Service Mesh mission welcome at install-network-service-mesh.json. Feel free to close if not relevant.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue points to the external console-kb definition at fixes/cncf-install/install-network-service-mesh.json and the KubeStellar Console mission. Read that definition and the linked console-marketplace and kc-agent repositories first. No concrete change or acceptance criteria are stated, so the intended definition of done is not established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100