KubeStellar Console Knowledge Base

The Knowledge Base is the library behind KubeStellar Console’s AI Missions system. It contains 400+ ready-to-use mission prompts that install, configure, troubleshoot, and repair open source Kubernetes projects across your multi-cluster fleet — all powered by AI that saves you time and tokens.

Two Types of Mission Prompts

Every mission prompt in the Knowledge Base falls into of two classes:

Installation Missions

Installation missions walk you through deploying a CNCF or open source project on or more clusters. Each installation mission includes:

• Prerequisites — What needs to be in place before installing (Helm, specific CRDs, minimum Kubernetes version)
• Installation steps — Step-by-step commands with explanations
• Configuration options — Common configuration parameters and when to use them
• Verification — How to confirm the installation succeeded
• Uninstall steps — Clean removal instructions
• Upgrade path — How to upgrade to newer versions

Example: Installing Prometheus across a multi-cluster fleet

Mission: Install Prometheus
Type: install
Difficulty: beginner
Target: All clusters matching label "monitoring=enabled"

Steps:
1. Add the prometheus-community Helm repo
2. Create the monitoring namespace
3. Install kube-prometheus-stack with recommended values
4. Verify Prometheus pods are running
5. Confirm metrics scraping is active

The AI executes each step, adapting to your specific cluster configuration. If a step fails, the AI diagnoses the issue and suggests a fix before continuing.

Solution Missions

Solution missions are troubleshooting and repair prompts. They start from a symptom — “pods crashing”, “high latency”, “certificate expired” — and guide the AI through diagnosis and repair.

• Symptom description — What the problem looks like
• Diagnostic steps — Commands to gather information
• Root cause analysis — AI interprets the diagnostic output
• Repair actions — Specific fixes with approval gates
• Verification — Confirm the fix worked
• Resolution saving — Save the solution for future reuse

Example: Repairing certificate expiry across clusters

Mission: Fix Expired TLS Certificates
Type: repair
Difficulty: intermediate
Symptom: Services returning TLS handshake errors

Steps:
1. Scan all clusters for expired certificates
2. Identify which cert-manager issuers are affected
3. Trigger certificate renewal
4. Verify new certificates are propagated
5. Confirm services are healthy

How AI Missions Work

When you run a mission from the Knowledge Base, here’s what happens:

1. You pick a mission — Browse the Knowledge Base or describe your problem in natural language
2. AI reads the prompt — The mission prompt gives the AI context, steps, and expected outcomes
3. AI adapts to your environment — The AI checks your actual cluster state (namespaces, versions, resources) and adjusts the steps
4. Step-by-step execution — Each step runs with your approval. The AI shows what it will do before doing it
5. Automatic error recovery — If a step fails, the AI diagnoses the failure and tries an alternative approach
6. Resolution saved — After success, the resolution is saved to your personal or shared Knowledge Base for future reuse

Multi-Cluster Awareness

Unlike single-cluster tools, every Knowledge Base mission is multi-cluster aware:

• Cluster selection — Choose which clusters to target (by name, label, or “all”)
• Parallel execution — Run the same mission across multiple clusters simultaneously
• Drift detection — The AI identifies differences between clusters and adapts
• Fleet-wide verification — Confirm results across all targeted clusters, not just

CNCF Projects in the Knowledge Base

The Knowledge Base includes installation and solution missions for projects across all CNCF categories. Here’s what’s currently available:

Observability & Monitoring

Networking & Service Mesh

Security & Policy

Storage & Data

Application Delivery & GitOps

Runtime & Orchestration

Infrastructure & Provisioning

Resolution Knowledge Base

Beyond the pre-built missions, the Knowledge Base grows with every problem you solve. The Resolution Knowledge Base tracks successful troubleshooting outcomes so you never solve the same problem twice.

How It Works

1. Complete a mission — After the AI successfully repairs an issue, you’re prompted to save the resolution
2. Save with context — The resolution captures the symptom, diagnostic steps, root cause, and fix
3. Personal or shared — Keep resolutions private or share with your organization
4. Automatic matching — When a similar problem occurs, the Knowledge Base suggests matching past resolutions
5. One-click reapply — Apply a previous resolution to a new occurrence with a single click

Personal vs Shared Resolutions

Over time, the shared Knowledge Base becomes an institutional memory of how your organization operates Kubernetes — a living runbook that the AI can reference automatically.

Browsing the Knowledge Base

Open the Mission Browser from the console sidebar or the AI Missions panel.

Filtering and Search

• By mission type — Install, troubleshoot, repair, upgrade, deploy, analyze
• By CNCF category — Observability, networking, security, storage, runtime
• By maturity — Graduated, incubating, sandbox
• By difficulty — Beginner, intermediate, advanced
• By tags — Specific technologies, use cases, or symptoms
• Full-text search — Search across mission titles, descriptions, and steps

Mission Sources

Missions come from three sources:

Deep Linking

Every mission has a permanent URL you can share:

https://console.kubestellar.io/missions/install-prometheus
https://console.kubestellar.io/missions/fix-certificate-expiry

Share mission links in Slack, documentation, or runbooks to give your team instant access to proven solutions.

Creating Custom Missions

You can create your own missions and add them to the Knowledge Base:

1. From natural language — Describe what you want to accomplish and the AI generates a mission
2. From a template — Start from an existing mission and modify it
3. From YAML/JSON — Import a mission definition file
4. From a resolution — Convert a successful troubleshooting session into a reusable mission

Custom missions follow the same format as community missions and can be shared via the Marketplace or GitHub.

Why This Saves You Time and Tokens

Traditional Kubernetes troubleshooting means:

1. Google the error message
2. Read 5 Stack Overflow answers
3. Try each suggestion manually
4. Repeat across every affected cluster

With the KubeStellar Console Knowledge Base:

1. AI matches the symptom to a known resolution
2. Executes the fix across all affected clusters in parallel
3. Verifies the fix worked everywhere

The result: What used to take hours of manual debugging now takes minutes of AI-guided resolution — across your entire multi-cluster fleet. And because mission prompts are optimized for the AI model, you use fewer tokens per resolution than free-form chat, saving both time and cost.