Multigres Kubernetes Operator
Direct pod management instead of StatefulSets enables drain-safe rolling updates.
SpotVortex is an open-source Kubernetes operator for one hard problem: getting Spot savings without gambling on reliability.
Transition-aware TFT model tracks market hazard before scaling Spot node pools.
SRE teams, FinOps engineers, Kubernetes operators on AWS
Karpenter · Goldilocks · Kubecost
SpotVortex runs inside the cluster and controls Spot at the node-pool level. It watches market risk and pool health, then decides when a pool should grow, spot, hold, freeze, or move back toward On-Demand.
A few concrete details about the shipped runtime:
* The deterministic mode is the active path * The control cadence is 10 minutes * Decisions stay at the node-pool level, not the pod level * Workload data stays in-cluster.
The controller also looks at pool blast radius, not just price. It tracks things like:
* PDB Slack under node loss * How much critical workload is sitting on the Spot restart and recovery time * Stateful workload mix * zone spread * evictability * available On-Demand headroom * Current AWS support is explicit. The shipped model scope covers 60 instance families across:
compute: c5, c6, c7 general purpose: m5, m6, m7 memory optimized: r5, r6, r7 burstable: t2, t3, t4g
Happy to answer hard questions.
Direct pod management instead of StatefulSets enables drain-safe rolling updates.
Kubernetes CRDs for AI agents, but pre-release status limits production use.
Declarative identity management via Kubernetes manifests is genuinely useful for Kanidm users.
C# operator for SurrealDB fills a gap where most operators are Go-based.
Feature-rich Kite dashboard adds AI agent layer, but Kubernetes dashboards are well-served by Lens, Rancher, Kubeflow.
Manual approval workflow adds safety gate Chaos Mesh and Litmus don't prioritize.