k9s

Navigate and debug Supabase V3 Kubernetes clusters with k9s.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/matt-metivier/zk-hub --skill k9s
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: k9s
Source: https://github.com/matt-metivier/zk-hub/tree/main/skills/general/infrastructure/k9s
Command: npx skills add https://github.com/matt-metivier/zk-hub --skill k9s

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Live exploration and debugging of Supabase V3 Kubernetes clusters is tedious with raw tooling; k9s provides a fast terminal UI to observe pod states, resources, and operator activity.

Core Features & Use Cases

  • Real-time navigation across namespaces, pods, and resources
  • View logs, shell into pods, and inspect SupabaseProject CRDs
  • Monitor operator reconcile loops and per-project namespaces

Quick Start

Launch k9s with your ESC-enabled kubeconfig to connect to your V3 cluster.

Frequently Asked Questions about k9s

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

FAQPage Schema
How do I debug a Supabase V3 Kubernetes cluster in real time?

Debug a Supabase V3 Kubernetes cluster by launching k9s with an ESC-enabled kubeconfig to navigate namespaces, inspect pod states, and monitor operator reconciliation activity live.

How do I monitor operator reconciliation loops across Supabase project namespaces?

Monitor operator reconciliation loops by using k9s to navigate per-project namespaces and observe SupabaseProject CRDs alongside pod resource states in real time.

What do I need to inspect Kubernetes pods and resources for Supabase deployments?

Inspecting Kubernetes pods for Supabase deployments requires a locally installed k9s binary, an ESC-enabled kubeconfig, and active access to the Supabase V3 cluster.

Can I view logs and shell into pods while troubleshooting Supabase Kubernetes resources?

Viewing logs and shelling into pods is supported directly within k9s to streamline live troubleshooting of Supabase Kubernetes resources and operator activity.

What is the best way to explore SupabaseProject CRDs without raw Kubernetes tooling?

Exploring SupabaseProject CRDs without raw tooling is best done through k9s, which provides a fast terminal UI to observe resources and operator activity across the cluster.