kobe 101: lease a Kubernetes cluster instead of creating one
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
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
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
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
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
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
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
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
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.
Cluster updates, in your inbox.
Kubernetes deep dives, GitOps field notes, and platform-engineering essays from the team building Kunobi. Two posts a month. No fluff.