DevOps Engineer Kafka & PostgreSQL

About Mirantis

Mirantis is the Kubernetes-native AI infrastructure company, enabling organizations to build and operate scalable, secure, and sovereign infrastructure for modern AI, machine learning, and data-intensive applications. By combining open source innovation with deep expertise in Kubernetes orchestration, Mirantis empowers platform engineering teams to deliver composable, production-ready developer platforms across any environment—on-premises, in the cloud, at the edge, or in sovereign data centers. As enterprises navigate the growing complexity of AI-driven workloads, Mirantis delivers the automation, GPU orchestration, and policy-driven control needed to manage infrastructure with confidence and agility. Committed to open standards and freedom from lock-in, Mirantis ensures that customers retain full control of their infrastructure strategy.

Mirantis, an IREN company, is the Kubernetes-native AI infrastructure company, enabling organizations to build and operate scalable, secure, and sovereign infrastructure for modern AI, machine learning, and data-intensive applications. By combining open-source innovation with deep expertise in Kubernetes orchestration, Mirantis empowers platform engineering teams to deliver composable, production-ready developer platforms across any environment — on-premises, in the cloud, at the edge, or in sovereign data centers.

As enterprises navigate the growing complexity of AI-driven workloads, Mirantis delivers the automation, GPU orchestration, and policy-driven control needed to manage infrastructure with confidence and agility. Committed to open standards and freedom from lock-in, Mirantis ensures that customers retain full control of their infrastructure strategy.

Job Description

We are looking for an experienced DevOps Engineer to own the deployment, release, and reliability backbone of the k0rdent-ai platform — our multi-tenant control plane for enterprise GPU infrastructure. The platform’s core services — identity (Keycloak), API gateway (Kong), workflow engine (Temporal), a suite of Go APIs, and the PostgreSQL databases behind them — run on every control-plane and regional cluster we operate, and must be upgraded safely, observed continuously, and recovered quickly.

You will run this platform across both cloud Kubernetes (AWS) and bare-metal clusters in our data centers, delivering it through Helm charts and k0rdent ServiceTemplates and MultiClusterServices. Beyond day-to-day operations, a substantial focus of this role is engineering the foundations that stateful services depend on: snapshot-capable storage (CSI drivers, StorageClasses, volume snapshots), CloudNativePG backups and point-in-time recovery, and the CI/CD and bare-metal end-to-end pipelines that validate every change before it reaches customers.

Because this platform holds the record of every tenant, user, and cluster action, this role also owns its operational readiness — runbooks, restore drills, and the upgrade and rollback paths that keep a failed release from turning into data loss.

Main Responsibilities

Multi-Environment Kubernetes Operations: Deploy, upgrade, and operate k0s / k0rdent-managed Kubernetes clusters on AWS and on bare-metal hardware, across a global control plane and multiple regions — cluster lifecycle, node maintenance, capacity planning, and version upgrades.

Helm & Service Delivery: Author and maintain Helm charts and k0rdent ServiceTemplates and MultiClusterServices for core services (Keycloak, Kong, Temporal, CloudNativePG, and in-house Go APIs), including dependency ordering, health gating, versioning, and zero-downtime upgrade paths.

Storage & Snapshot Engineering: Design and run Kubernetes storage for each environment — AWS EBS CSI in the cloud; OpenEBS LocalPV, Longhorn, or Ceph on bare metal — including StorageClasses, reclaim policies, the CSI snapshot controller, and VolumeSnapshotClasses, so stateful services can be snapshotted and restored reliably.

Database Backup & Recovery: Operate CloudNativePG backup and recovery end to end — scheduled volume snapshots, continuous WAL archiving to object storage, point-in-time recovery, and replica clusters — with defined RPO/RTO targets and regular restore drills.

CI/CD & End-to-End Testing: Build and maintain GitHub Actions pipelines for linting, chart unit tests, artifact packaging and publishing to OCI registries, and on-demand bare-metal end-to-end environments; keep them fast, reliable, and easy to debug.

GitOps & Infrastructure as Code: Maintain a strictly declarative infrastructure-as-code (IaC) culture using Terraform and Argo CD (or Flux), keeping every environment — from developer labs to production — reproducible and reviewable through code.

Observability & Incident Response: Build monitoring and alerting (Prometheus, Grafana, OpenTelemetry) for service health, database replication and backup status, and capacity; join the on-call rotation, lead troubleshooting, and drive post-incident improvements.

Security & Air-Gapped Delivery: Manage TLS and certificate lifecycle (cert-manager), secrets, network policies, and least-privilege RBAC, and support private-registry and air-gapped installations for sovereign customers.

 

Qualifications

Must Have

Platform Experience: 8+ years in DevOps, SRE, or platform engineering, including 3+ years operating production Kubernetes for business-critical services.

Kubernetes Depth: Strong grasp of Kubernetes primitives — workloads and StatefulSets, operators and CRDs, persistent volumes and CSI storage, RBAC, and network policies — with hands-on experience upgrading and troubleshooting clusters in production.

Helm & Release Engineering: Hands-on authoring of non-trivial Helm charts — templating, values design, chart dependencies, and testing with helm-unittest or chart-testing. Experience with k0rdent, Cluster API, or a multi-cluster delivery tool (Argo CD ApplicationSets, Fleet, Sveltos) is preferred, but what matters is depth with Helm, not the specific delivery tool.

Kubernetes Storage: Practical experience with CSI drivers, StorageClasses, and volume snapshots — AWS EBS CSI preferred, but equivalent experience with Longhorn, Ceph (Rook), OpenEBS, or another cloud CSI driver is acceptable. What matters is understanding how storage behaves when pods, nodes, and clusters fail.