skills.rest
projectbluefin
projectbluefinOFFICIAL
Explore all skills by this author →
WebsiteGitHub

console-dashboard

Deploy and operate the KubeStellar Console dashboard via ArgoCD GitOps on a k3s cluster.

11|9|Updated May 25, 2026
Search Tags:#dashboard#kubernetes#helm#gitops#argocd#k3s#kubestellar
One-click install
npx skills add https://github.com/projectbluefin/lab --skill console-dashboard-projectbluefin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: console-dashboard
Source: https://github.com/projectbluefin/lab/tree/main/docs/skills/console-dashboard
Command: npx skills add https://github.com/projectbluefin/lab --skill console-dashboard-projectbluefin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Operating the KubeStellar Console on a local k3s cluster involves many failure-prone details: pinned chart versions, RWO storage constraints, auth policy, RBAC for custom surfaces, and a strict GitOps vs imperative action split. This Skill encodes those operational rules so deployments, upgrades, and dashboard wiring stay consistent and recoverable. ## Core Features & Use Cases - GitOps-managed deployment: Deploy and upgrade the Console through the ArgoCD Application with pinned chart versions and lab-specific Helm values (Recreate strategy, disabled backups, ClusterIP service). - Dashboard surface wiring: Configure the enabledDashboards allowlist, marketplace cards, missions, and the lab-surfaces ClusterRole for ArgoCD, Argo Workflows, and KubeVirt CRD views. - Failure diagnosis: A symptom-to-fix table covers PVC deadlocks, stale JWT auth loops, missing metrics.k8s.io RBAC, and absent Node Feature Discovery labels. - Use Case: When the Console shows sample data instead of the ghost cluster after an upgrade, use this Skill to identify the kubeconfig misconfiguration and verify /health reports in_cluster: true. ## Quick Start Ask the agent to verify the KubeStellar Console deployment values and diagnose why a dashboard surface shows no resources.

Frequently Asked Questions about console-dashboard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy the KubeStellar Console with ArgoCD?▼

Deploy the Console through the ArgoCD Application defined in argocd/kubestellar-console-app.yaml, which pulls the pinned kubestellar-console chart from the upstream Helm repository. Never apply it manually; all desired-state changes go through Git for ArgoCD reconciliation.

How do I expose the KubeStellar Console securely?▼

Access the Console via kubectl port-forward to the ClusterIP service on port 8080. Before any ingress exposure, create a GitHub OAuth app, store credentials in a Secret referenced via github.existingSecret, and restrict allowedGitHubLogins; dev-mode anonymous admin must never be exposed.

Why does the KubeStellar Console show sample data instead of my cluster?▼

Sample data appears when chart kubeconfig values are set, which makes /health report in_cluster: false and routes cards to demo fallbacks. Remove the kubeconfig values and clear stale browser auth state such as kc-demo-mode after the rollout.

Why is the Console pod stuck after an upgrade?▼

A pod stuck in ContainerCreating usually means the deployment strategy reverted to RollingUpdate with a ReadWriteOnce PVC, causing a mount deadlock. Keep strategy.type set to Recreate and backup.enabled set to false because the backup PVC hardcodes ReadWriteMany.

Why do CPU and memory monitors show zero in the Console?▼

Zero metrics mean the Console ServiceAccount lacks list permission on nodes and pods in metrics.k8s.io, even when metrics-server itself is healthy. Retain that scoped read permission in the kubestellar-console-lab-surfaces ClusterRole.

When should actions go through GitOps versus the Console directly?▼

Declarative changes like app installs and BindingPolicy edits go through Git pull requests for ArgoCD to sync. Runtime operations like VM start/stop, workflow resubmits, and pod logs are performed imperatively by the Console through its ServiceAccount.

Related Skills

Explore More Software Engineering Skills→
unixfgunixfg

k3s-gitops

Manage a 3-node k3s cluster with GitOps, ArgoCD, and Longhorn.

Community
Advanced
spigellspigell

k8s-kubevirt

Manage KubeVirt virtual machines on Kubernetes with lifecycle operations and status checks.

Community
Intermediate
AO-HySAO-HyS

verify-aohys

Verifies aohys.com product surfaces with Computer Use execution and evidence-backed acceptance records.

Official
Advanced
phuetzphuetz
30

kubernetes

Consolidate kubectl, Helm, and ArgoCD workflows for Kubernetes cluster administration.

Community
Advanced