License

Created By
bourbonkka year ago
Kubernetes Control Plane Server for Managing Multiple Clusters – the central pilot for your k8s fleets
Overview

What is k8s-pilot?

k8s-pilot is a centralized control plane server designed for managing multiple Kubernetes clusters efficiently. It acts as the central pilot for your Kubernetes fleets, allowing users to observe and control all clusters from a single interface.

How to use k8s-pilot?

To use k8s-pilot, clone the repository from GitHub, install the required dependencies, and run the server using the provided commands. Ensure you have access to your Kubernetes clusters configured in your kubeconfig file.

Key features of k8s-pilot?

  • Multi-cluster context switching for seamless management.
  • CRUD operations on various Kubernetes resources including Deployments, Services, and Pods.
  • Integration with MCP for enhanced functionality.

Use cases of k8s-pilot?

  1. Managing multiple Kubernetes clusters from a single interface.
  2. Performing context-aware operations across clusters.
  3. Simplifying resource management and deployment processes.

FAQ from k8s-pilot?

  • Can k8s-pilot manage any Kubernetes cluster?

Yes, k8s-pilot can manage any Kubernetes cluster as long as you have the appropriate access configured.

  • What are the prerequisites for using k8s-pilot?

You need Python 3.13 or higher and the uv package manager installed.

  • Is k8s-pilot open source?

Yes, k8s-pilot is open source and available on GitHub.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
bourbonkk
Star
0
Language
Python
License
Apache-2.0 license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago