cyphernetes

I'm working on the next release of Cyphernetes. It's a query language for Kubernetes that allows doing most complex k8s management operations in a much more compact and concise form (compared to writing shell scripts, using jsonpath+jq, nested kubectl, writing API code etc.). Recently merged a visual overhaul to the Cyphernetes web UI and now working on adding support for ORDER BY, LIMIT and SKIP to the language. Github: https://github.com/AvitalTamir/cyphernetes

go run github.com/avitaltamir/cyphernetes/cmd/cyphernetes@v0.14.0 --help

I’m working on Cyphernetes [1] which is a new query language for working with the Kubernetes API with a focus on highly connected operations. It’s inspired by Neo4j’s Cypher and views Kubernetes as a connected graph of resources. It allows querying multiple resource kinds via their relationships (i.e. replicaset owns pod, service exposes deployment…) and easily crafting custom response payloads. Lately I’ve introduced aggregation functions and the ability to visualize query results using ascii art. This is a daily driver for me and I’m now mostly focused around features that will make it a complete kubectl alternative. [1] https://github.com/AvitalTamir/cyphernetes/

I created this tool around six months ago and it's been a daily driver for me since. I lets you use a syntax similar to Cypher(Neo4j's query language which I very much adore) to perform CRUD operations on K8s. This is an alpha release and while Cyphernetes has been in real-world use by me and a handful of other folk, I'd suggest extreme care when performing create/update/delete operations.

I'm excited to share Cyphernetes, a CLI tool I've developed to enhance Kubernetes management. My aim was to create a more declarative approach to handling complex Kubernetes operations. I'm a big fan of Neo4J's Cypher query language and believe it can lend itself well to the infrastructure domain. Drawing inspiration from the Cypher query language, Cyphernetes allows you to describe intricate Kubernetes tasks in a single, clear statement. I believe this approach can significantly streamline heavy Kubernetes operations, allow power-users to easily join data across resource kinds in Kubernetes and much more. The project is at it's earliest milestone and supports performing GET operations using MATCH queries. The Cypher-like grammar implementation is incomplete - However using this today already "felt like something" so I decided to put this