Skip to main content

Kubernetes Admin

Posted 15 days ago

ace stackSan Jose (CA)

SENIORITY

Senior

Apply (opens in a new tab)

About the role

Kubernetes AdministratorKubernetes Administrator to manage and optimize production clusters across Amazon EKS and Google Anthos/GKE. Responsible for cluster operations including upgrades, RBAC, autoscaling, ingress controllers (NGINX, ALB Ingress), networking policies, and security hardening. Implement and maintain observability stacks using Prometheus, Grafana, and Splunk for monitoring, alerting, and log analytics. Build and maintain CI/CD pipelines using ArgoCD, Jenkins, GitHub Actions, and Bitbucket to enable GitOps-driven deployments. Infrastructure provisioning and automation will be managed through Terraform modules following IaC best practices. Strong experience with AWS services including VPC, IAM, EC2, S3, Route 53, ELB/ALB, ECR, CloudWatch, KMS, and Secrets Manager is required. The ideal candidate brings 5+ years of Kubernetes experience, multi-cloud administration skills, hands-on Terraform expertise, and a solid understanding of CI/CD, GitOps, and cloud-native observability principles.

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.

More like this