# Kunobi

> Kunobi is a desktop Kubernetes & GitOps management platform — the Ninja Command Center for Kubernetes and GitOps. It provides real-time visibility and operational control over Kubernetes deployments at scale, working natively with FluxCD and ArgoCD without replacing them or breaking GitOps best practices. Available for macOS (Intel & Apple Silicon), Windows, and Linux.

## LLM-readable content

- [All documentation, blog posts, and changelogs](https://kunobi.com/llms-full.txt)
- [Kache documentation](https://kunobi.com/llms/kache.txt)
- [Kobe documentation](https://kunobi.com/llms/kobe.txt)
- [Kunobi documentation](https://kunobi.com/llms/kunobi.txt)
- [Ping documentation](https://kunobi.com/llms/ping.txt)
- Add `.md` to any documentation URL for that page as Markdown. Example: [Kunobi getting started](https://kunobi.com/docs/kunobi/getting-started.md)

## Docs

- [Benchmarks and reports](https://kunobi.com/docs/kache/benchmarks): Measure cold, local-hit, remote-hit, and cross-checkout behavior
- [Deduplication](https://kunobi.com/docs/kache/deduplication): How Kache shares output bytes and restores them safely
- [Kache](https://kunobi.com/docs/kache): A local-first compiler cache for Rust and C/C++ builds
- [Monitor](https://kunobi.com/docs/kache/monitor): Read live cache, build, storage, and transfer state
- [Remote planner service](https://kunobi.com/docs/kache/remote-service): Preview service for ranking cache entries to prefetch
- [kobe](https://kunobi.com/docs/kobe): Pre-warmed Kubernetes cluster pools for instant CI and developer environments.
- [Account & Login](https://kunobi.com/docs/kunobi/account): Sign in to Kunobi and manage your account
- [AI Assistant](https://kunobi.com/docs/kunobi/ai-conversations): Chat with a Kubernetes-aware AI assistant directly inside Kunobi
- [Bitbucket](https://kunobi.com/docs/kunobi/bitbucket): See and change who can reach which Bitbucket repository - user groups, members, repositories, and every permission grant with the path that produced it
- [Ceph](https://kunobi.com/docs/kunobi/ceph): Connect Ceph clusters to Kunobi - health, capacity, hosts, OSDs, pools, RBD block storage, events, alerts and silences
- [Cilium](https://kunobi.com/docs/kunobi/cilium): Inspect a Cilium CNI - policies, endpoints, BGP, encryption, and agent diagnostics
- [Cloud Providers](https://kunobi.com/docs/kunobi/cloud-providers): Pull cluster kubeconfigs from managed-Kubernetes services
- [Cloudflare](https://kunobi.com/docs/kunobi/cloudflare): Browse and manage your Cloudflare accounts - zones, DNS records, Workers, tunnels, load balancing, R2, cache and analytics
- [Extensions](https://kunobi.com/docs/kunobi/extensions): Install and manage the extensions that expand Kunobi beyond core Kubernetes
- [Feedback & Support](https://kunobi.com/docs/kunobi/feedback): Help shape Kunobi's future by sharing your feedback
- [Installation & Updates](https://kunobi.com/docs/kunobi/getting-started): Install Kunobi, choose a release channel, and keep it up to date
- [Introduction](https://kunobi.com/docs/kunobi): What Kunobi is and what you can do with it
- [Interface & Navigation](https://kunobi.com/docs/kunobi/interface): Get around the Kunobi window - panels, tabs, windows, and the command palette
- [Keybindings & Shortcuts](https://kunobi.com/docs/kunobi/keybindings): Master Kunobi with keyboard shortcuts and the command palette
- [License Agreement](https://kunobi.com/docs/kunobi/license-agreement): How to accept and view Kunobi's license agreement
- [MCP Server & Automation](https://kunobi.com/docs/kunobi/mcp): Expose your cluster to external AI clients through Kunobi's built-in MCP server
- [Plans & Pro](https://kunobi.com/docs/kunobi/plans): What the free tier includes, what Pro unlocks, and how licensing works
- [RBAC](https://kunobi.com/docs/kunobi/rbac): See who your cluster thinks you are and exactly what your account is allowed to do
- [Redfish](https://kunobi.com/docs/kunobi/redfish): Monitor and control physical servers through their BMC - health, inventory, event logs, power and boot control
- [Release Channels](https://kunobi.com/docs/kunobi/release-channels): Choose how you receive Kunobi updates
- [SNMP](https://kunobi.com/docs/kunobi/snmp): Monitor network devices over SNMP - polling, interfaces, an OID browser, and MIB name resolution
- [Sources](https://kunobi.com/docs/kunobi/sources): Manage the connections Kunobi makes outside Kubernetes - add, test, connect, and remove them from one page
- [Telemetry](https://kunobi.com/docs/kunobi/telemetry): Understanding anonymous usage statistics in Kunobi
- [Get started](https://kunobi.com/docs/ping/getting-started): From zero to your first push notification in about five minutes — create a key, connect your monitoring tool, install the app.
- [Kunobi Ping](https://kunobi.com/docs/ping): Turn any monitoring alert into a push notification on your phone. Connect Grafana, SigNoz, Prometheus and more in minutes — no Slack relay, no bot to babysit.
- [Connect your monitoring](https://kunobi.com/docs/ping/providers): Point Grafana, SigNoz, Prometheus Alertmanager, and other tools at Ping — each one posts to its own URL so every alert reads correctly.
- [Teams & who gets alerted](https://kunobi.com/docs/ping/teams): How Ping decides who to notify — personal teams, shared teams, and how your phone is matched to you automatically.
- [Command reference](https://kunobi.com/docs/kache/commands/reference): Every top-level Kache command, its purpose, and common flags
- [Daemon lifecycle](https://kunobi.com/docs/kache/daemon/lifecycle): Start, stop, install, update, and troubleshoot the daemon
- [Daemon overview](https://kunobi.com/docs/kache/daemon/overview): What the background daemon owns and what still works without it
- [C/C++ caching](https://kunobi.com/docs/kache/getting-started/c-cpp): Cache supported GCC, Clang, and clang-cl object compilations
- [Kache or sccache?](https://kunobi.com/docs/kache/getting-started/comparison): Choose a compiler cache based on the workflow you need
- [Configuration](https://kunobi.com/docs/kache/getting-started/configuration): Configure Kache with TOML files and environment variables
- [Installation](https://kunobi.com/docs/kache/getting-started/installation): Install Kache from a release, package manager, crates.io, or Nix
- [Mutation testing](https://kunobi.com/docs/kache/getting-started/mutation-testing): Run cargo-mutants after kache init and know what the cache saves
- [Quick start](https://kunobi.com/docs/kache/getting-started/quick-start): Enable Kache and verify reuse between two worktrees
- [Architecture](https://kunobi.com/docs/kache/how-it-works/architecture): How the compiler wrapper, local store, and daemon divide the work
- [Cache key](https://kunobi.com/docs/kache/how-it-works/cache-key): Inputs, normalization, and tools for explaining a cache miss
- [Limits](https://kunobi.com/docs/kache/how-it-works/limits): How Kache paces concurrent compiler processes without wrapping Cargo
- [Bound a remote](https://kunobi.com/docs/kache/remote-cache/bounding): Let the store expire old objects; kache never deletes remotely
- [CI setup](https://kunobi.com/docs/kache/remote-cache/ci): Use Kache in GitHub Actions or a shell-based CI job
- [Filesystem setup](https://kunobi.com/docs/kache/remote-cache/filesystem-setup): Use a mounted directory as the remote cache
- [S3 setup](https://kunobi.com/docs/kache/remote-cache/s3-setup): Connect Kache to AWS S3 or an S3-compatible service
- [Sync](https://kunobi.com/docs/kache/remote-cache/sync): Pull and push cache entries without the daemon
- [API reference](https://kunobi.com/docs/kobe/api/reference): All HTTP endpoints with request and response shapes.
- [Command reference](https://kunobi.com/docs/kobe/commands/reference): All kobe CLI commands with flags and examples.
- [Executable resource commands](https://kunobi.com/docs/kobe/commands/sandbox): Lease and operate resources according to the capabilities exposed by their pool.
- [Configuration](https://kunobi.com/docs/kobe/getting-started/configuration): CLI config file, environment variables, and per-command overrides.
- [Installation](https://kunobi.com/docs/kobe/getting-started/installation): How to install the kobe CLI.
- [Quick start](https://kunobi.com/docs/kobe/getting-started/quick-start): Configure the kobe CLI, lease your first cluster, and release it when done.
- [OIDC](https://kunobi.com/docs/kobe/auth/oidc): Configure JWT-based authentication with GitHub Actions, Clerk, Auth0, or any OIDC provider.
- [Authentication](https://kunobi.com/docs/kobe/auth/overview): How AccessPolicy configures authentication and authorization for lease requests.
- [SSH keys](https://kunobi.com/docs/kobe/auth/ssh-keys): Authenticate with an Ed25519 SSH key via your SSH agent.
- [Architecture](https://kunobi.com/docs/kobe/how-it-works/architecture): The operator, HTTP API, pool manager, and runtime backends - and how a lease flows through them.
- [Pool lifecycle](https://kunobi.com/docs/kobe/how-it-works/pool-lifecycle): How pool instances move through Creating, Ready, Leased, and Recycling phases - and what triggers each transition.
- [Runtime strategy](https://kunobi.com/docs/kobe/how-it-works/runtime-strategy): Which virtual-cluster runtime kobe stands on today, where it is heading, and what is retired.
- [Backends](https://kunobi.com/docs/kobe/pools/backends): k3s, k0s, CAPI, and vcluster — how each backend provisions virtual clusters.
- [Pools](https://kunobi.com/docs/kobe/pools/overview): Define cluster templates with ClusterPool and control pool size, TTL, addons, and health checks.
- [Sandbox pools](https://kunobi.com/docs/kobe/pools/sandbox-pools): Define bounded, administrator-owned Agent Sandbox templates and placement.
- [Connecting to Clusters](https://kunobi.com/docs/kunobi/kubernetes/clusters): Discover, connect to, and manage your Kubernetes cluster connections
- [Drilldown](https://kunobi.com/docs/kunobi/kubernetes/drilldown): Navigate into related Kubernetes resources with context-aware drilldown actions
- [Filtering & Search](https://kunobi.com/docs/kunobi/kubernetes/filtering): Find Kubernetes resources fast with Kunobi's powerful filter syntax
- [GitOps](https://kunobi.com/docs/kunobi/kubernetes/gitops): Browse and manage FluxCD and ArgoCD resources with dependency graphs, bulk actions, and drilldown views
- [Kubernetes](https://kunobi.com/docs/kunobi/kubernetes): Connect to clusters and run day-to-day Kubernetes operations with Kunobi
- [Kubernetes Operations](https://kunobi.com/docs/kunobi/kubernetes/kubernetes-operations): Scale workloads, manage nodes, view Helm releases, sync ArgoCD apps, and more
- [Multi-Cluster Management](https://kunobi.com/docs/kunobi/kubernetes/multi-cluster): Connect and work with multiple Kubernetes clusters simultaneously
- [Terminal, Shells & Logs](https://kunobi.com/docs/kunobi/kubernetes/terminal): Use the integrated terminal, exec into pods, stream logs, and forward ports
- [Local Clusters](https://kunobi.com/docs/kunobi/kubernetes/try-kunobi): Create and manage local Kubernetes clusters to explore Kunobi
- [Workspaces](https://kunobi.com/docs/kunobi/kubernetes/workspaces): Organize your Kubernetes views with workspaces, filter presets, and per-tab layouts
- [AI & MCP](https://kunobi.com/docs/kunobi/settings/ai-mcp): Configure the MCP server and AI conversation integration
- [Context Watcher](https://kunobi.com/docs/kunobi/settings/context-watcher): Control how Kunobi monitors your .kube directory
- [General Settings](https://kunobi.com/docs/kunobi/settings/general): Configure auto-reconnect, auto-select cluster, keystroke display, and more
- [Overview](https://kunobi.com/docs/kunobi/settings): Configure Kunobi to match your preferences and workflow
- [Keybindings](https://kunobi.com/docs/kunobi/settings/keybindings): Customize keyboard shortcuts for every action in Kunobi
- [License Agreement](https://kunobi.com/docs/kunobi/settings/license-agreement): View the Kunobi Pre-Release License Agreement from Settings
- [Release Channel](https://kunobi.com/docs/kunobi/settings/release-channel): Choose which release channel to receive updates from
- [Telemetry](https://kunobi.com/docs/kunobi/settings/telemetry): Control anonymous usage statistics collection
- [Theme](https://kunobi.com/docs/kunobi/settings/theme): Change the color scheme and visual appearance of Kunobi
- [Tools](https://kunobi.com/docs/kunobi/settings/tools): Install and manage Kubernetes CLI tools from within Kunobi

## Blog

- [Kunobi Ping: your monitoring alerts, as push notifications](https://kunobi.com/blog/kunobi-ping-alerts-on-your-phone): Ping takes the alerts your monitoring tools already produce and delivers them to your phone as a native push notification, routed to a team, with an inbox you can triage and acknowledge. It is on the App Store and Google Play today.
- [Which key pays for gpt-4o? You probably can't answer that](https://kunobi.com/blog/agentgateway-extension): Provider order in a gateway config is a billing decision, and nothing in the config says so. Agent Gateway runs the agentgateway data plane inside Kunobi - loopback proxies speaking the OpenAI wire protocol, fronting every model and MCP server you use, with every secret in the OS keychain.
- [kobe 101: lease a Kubernetes cluster instead of creating one](https://kunobi.com/blog/kobe-101-leasing-kubernetes-clusters): kobe is a Kubernetes operator that keeps pools of clusters warm and hands them out as leases with a server-enforced TTL, so CI and developers get a clean, isolated cluster in seconds without a long-lived kubeconfig and without anyone owning the cleanup.
- [The Bitbucket access no permissions tab will show you](https://kunobi.com/blog/bitbucket-permissions): Answering 'who can push to this repository?' in Bitbucket means opening the members page, every group page, and every repository's permissions tab, then joining them by hand. The Bitbucket extension for Kunobi does that join: groups, members, repositories, and one row per permission grant, each carrying the derivation path that produced it.
- [Effective Kubernetes access with the RBAC extension](https://kunobi.com/blog/rbac-extension): The RBAC extension turns the Kubernetes SelfSubject review APIs into sortable tables: the identity the cluster authenticated, every permission it grants, and access broken down by namespace, so an account with limited access can see its own reach without reading a single RoleBinding.
- [Ceph clusters as first-class resources in Kunobi](https://kunobi.com/blog/ceph-extension): The Ceph extension pulls cluster health, capacity, OSDs, pools, block images, and alerts into Kunobi, rendered as the same sortable drilldown tables you already use for Kubernetes.
- [Connect to 14 Managed Kubernetes Providers Without Memorizing Their CLIs](https://kunobi.com/blog/cloud-providers-extension): The Cloud Providers extension turns the per-vendor install/authenticate/get-credentials routine into one screen: browse your cloud accounts, pick a cluster, and the kubeconfig lands in Kunobi ready to use.
- [Monitoring network devices and server hardware in Kunobi with the SNMP and Redfish extensions](https://kunobi.com/blog/snmp-extension): Two Kunobi extensions bring the hardware under your cluster into the same resource browser as Pods. The SNMP extension polls switches, routers and firewalls for device and interface status, every varbind named through a built-in MIB layer, and on-demand GET and WALK. The Redfish extension reads the physical servers through their management controllers - inventory, health sensors, firmware and event logs - and can also power, boot, and locate them.
- [The Cilium state kubectl will never see](https://kunobi.com/blog/cilium-extension): Most of Cilium's live state never reaches the Kubernetes API — it lives inside the agents, one SSH session per node. Here's how Kunobi reads both halves: the declared CRDs and the live agent state — identities, endpoints, BGP, encryption, Hubble, and Cluster Mesh — in one place.
- [AI and worktrees are filling our disks: kache storage, measured](https://kunobi.com/blog/kache-storage-worktrees): The way we build is shifting to many parallel worktrees, one per task and often driven by AI agents, and each is a full build tree on disk. A measured look at how kache shares those bytes: on APFS a second Firefox worktree restored 13.5 GB without copying one, and reflink sharing saved 27.4 GB.
- [Where Does My Traffic Go? Services, Selectors, and Readiness in Kubernetes](https://kunobi.com/blog/where-does-my-traffic-go): A Service can look completely healthy and still route to nothing. Here is how a Service decides which pods receive traffic, why a valid Service can route to nothing, and how to look at the set of pods behind it directly.
- [Designing a correct compile-cache key](https://kunobi.com/blog/kache-v0-5-0): A compile-cache key can fail two ways: too specific (needless recompiles) or too loose (wrong artifacts). How kache v0.5.0 corrects both, and what it does about inputs the compiler can never see.
- [kache v0.4.1: what it takes to trust a build cache](https://kunobi.com/blog/kache-v0-4-1): Two releases covering cache key correctness, three reliability hardening changes, experimental C/C++ caching, and first-class Windows support.
- [Cloud Repatriation Explained: Current Trends in Hybrid Infrastructure](https://kunobi.com/blog/cloud-repatriation-hybrid-infrastructure): Cloud repatriation has moved from niche debates into mainstream enterprise conversations. We look at what the data says, what engineers are actually struggling with, and why the real issue is operational clarity, not cloud vs on-prem.
- [Content-addressed Rust builds (or, what kache actually caches)](https://kunobi.com/blog/what-kache-actually-caches): How kache works under the hood: a RUSTC_WRAPPER with a content-addressed cache keyed by source, dependencies, and toolchain, restoring hits with reflinks and hardlinks across worktrees and CI.
- [kache 0.3.0: C/C++ build caching, crates.io, and the storage win](https://kunobi.com/blog/kache-update): kache 0.3.0 brings C/C++ object caching behind a conservative allow-list, reflink-first restores, Windows groundwork, and an in-progress crates.io name transfer, plus why storage savings matter as much as speed.
- [The Moment You Pipe kubectl logs Into grep, You've Already Lost](https://kunobi.com/blog/kubectl-logs-grep-problem): Why the grep-jq-pipe-repeat loop fails at 2:47 AM, and what a structured log interface changes about Kubernetes incident response.
- [Rolling Updates and Rollbacks in Kubernetes](https://kunobi.com/blog/rolling-updates): A Deployment doesn't manage pods directly. It manages ReplicaSets. Here's why that two-layer model makes zero-downtime updates and instant rollbacks possible, and how to watch the handover happen.
- [Kunobi v1.0.0 Is Here](https://kunobi.com/blog/kunobi-v1): After months of feedback, testing, fixing, and release-by-release improvements, Kunobi is now moving from beta to stable.
- [From Pending to CrashLoopBackOff: Understanding Every Pod Status](https://kunobi.com/blog/pod-lifecycle): CrashLoopBackOff isn't a pod phase. Neither is ImagePullBackOff. Here's what every pod status actually means, where in the lifecycle it breaks, and how to debug each one with a live demo.
- [Kubernetes Workspaces: Stop Rebuilding Your Dashboard View Every Time You Switch Context](https://kunobi.com/blog/kubernetes-workspaces): Every context switch costs you the setup time. Kunobi workspaces let you save and pin your cluster views so your filters, columns, and layouts are exactly where you left them.
- [Open-sourcing kache: a Rust build cache and sccache alternative](https://kunobi.com/blog/open-sourcing-kache): kache is a Rust build cache and sccache alternative for git worktrees, macOS, and CI, using hardlinks, blake3 content-addressing, and S3 sync.
- [KubeCon for First-Timers: What Actually Matters (And What Doesn't)](https://kunobi.com/blog/kubecon-first-timers): Attending KubeCon for the first time? A practical guide to navigating 12,000+ people, dozens of tracks, and the hallway conversations that matter most, with advice from CNCF Ambassadors who've been there.
- [Why kubectl Hangs for 30 Seconds on VPN (IPv6 + EKS Explained)](https://kunobi.com/blog/kubectl-vpn-timeout): kubectl taking 20-30 seconds on VPN? Learn how IPv6 dual-stack DNS and EKS endpoints cause hidden timeouts, and why Happy Eyeballs fixes it.
- [Why Your Kubernetes Tool Uses 1GB of RAM (and How to Fix It)](https://kunobi.com/blog/why-kubernetes-tool-uses-1gb-ram): Why Kubernetes desktop clients can reach 1GB+ RAM in multi-cluster GitOps setups — what causes it and what architectural alternatives exist.
- [A GUI for Your Flux CD Pipeline: See What GitOps Is Actually Doing](https://kunobi.com/blog/fluxcd_gui): Stop assembling the picture in your head. See your entire Flux CD pipeline as a live dependency graph.
- [Visualizing Helm Deployments to Debug Kubernetes Faster](https://kunobi.com/blog/visualize-helm): Stop juggling terminal tabs. See your entire Helm deployment at a glance with visual flow diagrams.
- [Why CLI vs GUI in Kubernetes Is the Wrong Debate](https://kunobi.com/blog/cli-vs-gui-wrong-debate): Is Kubernetes hard because of the tools, or because no one can see the whole system anymore? We explore why the CLI vs GUI debate misses the real issue: shared visibility in team-operated systems.
- [Kubernetes Resource Operations: From Inspection to Action](https://kunobi.com/blog/inspect-to-act): Managing Kubernetes resources typically requires multiple commands and context switches. See how Kunobi streamlines the view-edit-apply workflow into a single interface.
- [The 'Observer Effect' in GitOps: Why Pure Automation Isn't Enough](https://kunobi.com/blog/observer-effects-gitops): GitOps promises seamless automation, but when something breaks, the reconciliation process becomes a black box. Here's why visibility matters more than you think.
- [Flux vs Argo CD in Production: GitOps Operational Trade-offs at Scale](https://kunobi.com/blog/flux-vs-argocd): A production-focused comparison of Flux and Argo CD, examining real GitOps operational trade-offs around visibility, debugging, scale, and team onboarding.
- [Stop grep-ing Logs: Debugging Flux Syncs at the Speed of Sight](https://kunobi.com/blog/flux-debugging): Kubernetes is hierarchical. Your CLI isn't. It's time to see the graph.
- [Why GitOps Needs a Visual Layer (Without Breaking Its Purity)](https://kunobi.com/blog/gitops-visual-layer): You can't fix what you can't see — and GitOps was never meant to be blind. GitOps is about automation, but observability is human.
- [Test Kunobi's Flux-powered demo cluster and see live reconciliation in action](https://kunobi.com/blog/demo-cluster): Try Kunobi's instant Flux-powered Kubernetes demo — no setup, no cloud costs. Spin up a real GitOps cluster locally and see live reconciliation in action
- [Kunobi: Precision for Kubernetes. Mastery for GitOps.](https://kunobi.com/blog/hello-kunobi): Kubernetes transformed how we deploy and scale applications. It's powerful and flexible — but operating it at scale still demands focus, time, and patience it shouldn't.

## Changelog

- [v0.1.0-beta.10](https://kunobi.com/changelog/v0.1.0-beta.10): Release notes for Kunobi v0.1.0-beta.10
- [v0.1.0-beta.11](https://kunobi.com/changelog/v0.1.0-beta.11): Release notes for Kunobi v0.1.0-beta.11
- [v0.1.0-beta.12](https://kunobi.com/changelog/v0.1.0-beta.12): Release notes for Kunobi v0.1.0-beta.12
- [v0.1.0-beta.13](https://kunobi.com/changelog/v0.1.0-beta.13): Release notes for Kunobi v0.1.0-beta.13
- [v0.1.0-beta.14](https://kunobi.com/changelog/v0.1.0-beta.14): Release notes for Kunobi v0.1.0-beta.14
- [v0.1.0-beta.15](https://kunobi.com/changelog/v0.1.0-beta.15): Release notes for Kunobi v0.1.0-beta.15
- [v0.1.0-beta.16](https://kunobi.com/changelog/v0.1.0-beta.16): Release notes for Kunobi v0.1.0-beta.16
- [v0.1.0-beta.17](https://kunobi.com/changelog/v0.1.0-beta.17): Release notes for Kunobi v0.1.0-beta.17
- [v0.1.0-beta.18](https://kunobi.com/changelog/v0.1.0-beta.18): Release notes for Kunobi v0.1.0-beta.18
- [v0.1.0-beta.19](https://kunobi.com/changelog/v0.1.0-beta.19): Release notes for Kunobi v0.1.0-beta.19
- [v0.1.0-beta.20](https://kunobi.com/changelog/v0.1.0-beta.20): Release notes for Kunobi v0.1.0-beta.20
- [v0.1.0-beta.21](https://kunobi.com/changelog/v0.1.0-beta.21): Release notes for Kunobi v0.1.0-beta.21
- [v0.1.0-beta.22](https://kunobi.com/changelog/v0.1.0-beta.22): Release notes for Kunobi v0.1.0-beta.22
- [v0.1.0-beta.23](https://kunobi.com/changelog/v0.1.0-beta.23): Release notes for Kunobi v0.1.0-beta.23
- [v0.1.0-beta.24](https://kunobi.com/changelog/v0.1.0-beta.24): Release notes for Kunobi v0.1.0-beta.24
- [v0.1.0-beta.25](https://kunobi.com/changelog/v0.1.0-beta.25): Release notes for v0.1.0-beta.25
- [v0.1.0-beta.26](https://kunobi.com/changelog/v0.1.0-beta.26): Release notes for v0.1.0-beta.26
- [v0.1.0-beta.27](https://kunobi.com/changelog/v0.1.0-beta.27): Release notes for v0.1.0-beta.27
- [v0.1.0-beta.28](https://kunobi.com/changelog/v0.1.0-beta.28): Release notes for v0.1.0-beta.28
- [v0.1.0-beta.29](https://kunobi.com/changelog/v0.1.0-beta.29): Release notes for v0.1.0-beta.29
- [v0.1.0-beta.30](https://kunobi.com/changelog/v0.1.0-beta.30): Release notes for v0.1.0-beta.30
- [v0.1.0-beta.31](https://kunobi.com/changelog/v0.1.0-beta.31): Release notes for v0.1.0-beta.31
- [v0.1.0-beta.32](https://kunobi.com/changelog/v0.1.0-beta.32): Release notes for v0.1.0-beta.32
- [v0.1.0-beta.33](https://kunobi.com/changelog/v0.1.0-beta.33): Release notes for v0.1.0-beta.33
- [v0.1.0-beta.34](https://kunobi.com/changelog/v0.1.0-beta.34): Release notes for v0.1.0-beta.34
- [v0.1.0-beta.5](https://kunobi.com/changelog/v0.1.0-beta.5): Release notes for Kunobi v0.1.0-beta.5
- [v0.1.0-beta.6](https://kunobi.com/changelog/v0.1.0-beta.6): Release notes for Kunobi v0.1.0-beta.6
- [v0.1.0-beta.7](https://kunobi.com/changelog/v0.1.0-beta.7): Release notes for Kunobi v0.1.0-beta.7
- [v0.1.0-beta.8](https://kunobi.com/changelog/v0.1.0-beta.8): Release notes for Kunobi v0.1.0-beta.8
- [v0.1.0-beta.9](https://kunobi.com/changelog/v0.1.0-beta.9): Release notes for Kunobi v0.1.0-beta.9
- [v1.0.0](https://kunobi.com/changelog/v1.0.0): Release notes for v1.0.0 — Kunobi reaches general availability
- [v1.1.0-rc.1](https://kunobi.com/changelog/v1.1.0-beta.1): Release notes for v1.1.0-rc.1 — first unstable cut after the 1.0 GA
- [v1.1.0](https://kunobi.com/changelog/v1.1.0): Release notes for v1.1.0 — first stable cut on the post-1.0 track
- [v1.2.0-rc.1](https://kunobi.com/changelog/v1.2.0-rc.1): Release notes for v1.2.0-rc.1 — first unstable cut on the 1.2 track
- [v1.2.0](https://kunobi.com/changelog/v1.2.0): Release notes for v1.2.0 — the 1.2 stable release
- [v1.3.0-rc.1](https://kunobi.com/changelog/v1.3.0-rc.1): Release notes for v1.3.0-rc.1 — first unstable cut on the 1.3 track
- [v1.3.0-rc.2](https://kunobi.com/changelog/v1.3.0-rc.2): Release notes for v1.3.0-rc.2 — second unstable cut on the 1.3 track
- [v1.3.0](https://kunobi.com/changelog/v1.3.0): Release notes for v1.3.0 — the 1.3 stable release
- [v1.4.0-rc.1](https://kunobi.com/changelog/v1.4.0-rc.1): Release notes for v1.4.0-rc.1 — first unstable cut on the 1.4 track
- [v1.4.0](https://kunobi.com/changelog/v1.4.0): Release notes for v1.4.0 — the 1.4 stable release
- [v1.5.0-rc.1](https://kunobi.com/changelog/v1.5.0-rc.1): Release notes for v1.5.0-rc.1 — first unstable cut on the 1.5 track
- [v1.5.0-rc.2](https://kunobi.com/changelog/v1.5.0-rc.2): Release notes for v1.5.0-rc.2 — CLI agents in the console, git-provider Sources, and a rebuilt relationship graph
- [v1.5.0](https://kunobi.com/changelog/v1.5.0): Release notes for v1.5.0 — the 1.5 stable release
- [v1.6.0-rc.1](https://kunobi.com/changelog/v1.6.0-rc.1): Release notes for v1.6.0-rc.1 — MCP tool RBAC, editable Canvas, a NATS extension, and per-tab multi-source
- [v1.6.0-rc.2](https://kunobi.com/changelog/v1.6.0-rc.2): Release notes for v1.6.0-rc.2 — one-click MCP setup for AI clients, a GitHub Actions extension, editable Canvas boards, and fleet-wide Redfish/SNMP monitoring
- [v1.6.0](https://kunobi.com/changelog/v1.6.0): Release notes for v1.6.0 — the 1.6 stable release
- [v1.7.0-rc.1](https://kunobi.com/changelog/v1.7.0-rc.1): Release notes for v1.7.0-rc.1
- [v1.7.0-rc.2](https://kunobi.com/changelog/v1.7.0-rc.2): Release notes for v1.7.0-rc.2
- [v1.7.0](https://kunobi.com/changelog/v1.7.0): Release notes for v1.7.0 — the 1.7 stable release

## Features

- **Flux Remains the Engine**: Reconciliation, drift detection, and deployments are still handled by Flux. Kunobi does not replace it.
- **Git Stays the Control Plane**: Desired state lives in Git. Kunobi does not bypass or rewrite your existing workflows.
- **Real-time Visibility**: See reconciliation state, health, drift, and dependencies across clusters in one place.
- **Safe Control Actions Only**: Trigger syncs and observe changes without introducing proprietary logic or lock-in.
- **Zero Cluster Footprint**: No agents, no operators, no sidecars. Kunobi connects through your existing kubeconfig — the same way kubectl does.
- **Multi-cluster from Day One**: Switch contexts, compare states, and see what is deployed where. FluxCD and ArgoCD are first-class citizens, not plugins.
- **One Window, Not Twelve Tabs**: Resources, logs, terminal, and diagnostics all in one place. No more bouncing between tools to answer one question.
- **Native Desktop App**: Built with Tauri — starts fast, stays light. Credentials live in your system keychain, not in browser storage. No cloud account required.
- **Try Without a Cluster**: Spin up a demo cluster from inside Kunobi and explore a fully working GitOps environment in minutes.
- **MCP Server for AI Tools**: Kunobi exposes read-only cluster access to tools like Claude Code, so your AI assistant can understand your infrastructure without copying YAML back and forth.

## Key Pages

- [Download](https://kunobi.com/download): Download Kunobi for macOS, Windows, or Linux
- [Why Kunobi](https://kunobi.com/why-kunobi): Product manifesto and value proposition
- [Compare](https://kunobi.com/compare): Kunobi compared to other Kubernetes management tools
- [Pricing](https://kunobi.com/pricing): Pricing information
- [Changelog](https://kunobi.com/changelog): Release notes and version history
- [Contact](https://kunobi.com/contact): Get in touch with the team

## Legal

- [Privacy Policy](https://kunobi.com/privacy/web): Web application privacy policy
- [Terms of Use](https://kunobi.com/terms-of-use): Terms and conditions
- [Cookie Policy](https://kunobi.com/cookies-policy): Cookie usage information
- [EULA](https://kunobi.com/eula): End User License Agreement for the desktop app (always the current version)
- [App Privacy Policy](https://kunobi.com/privacy/desktop): Privacy policy for the desktop app (always the current version)