Kubernetes & Platform Engineering
Kubernetes ships a new minor version roughly every four months and managed services retire old ones on a fixed calendar. We keep clusters supported, build platforms developers actually like using and remove the toil around them.

Dates that drive this work
- days Amazon EKS Kubernetes 1.31 leaves EKS extended support; remaining clusters are auto-upgraded.ics
- days Azure AKS Kubernetes 1.34 reaches end of life on AKS (community support).ics
- days Amazon EKS Kubernetes 1.34 ends standard support on EKS; extended-support billing starts.ics
- days Google GKE Kubernetes 1.34 ends standard support on GKE.ics
Sources: Microsoft Learn: Supported Kubernetes versions in AKS, AWS: Kubernetes version lifecycle on Amazon EKS, Google Cloud: GKE release schedule
Sound familiar?
- EKS clusters are paying for extended support, or will be auto-upgraded when it ends.
- AKS and GKE will upgrade clusters on their own schedule if you do not, and deprecated APIs will break on the way.
- Every team built its own cluster and pipeline, and nobody can upgrade them all.
- Developers wait days for environments that should take minutes.
What you receive
- Cluster inventory with support dates
- Deprecated API and add-on report
- Upgrade runbooks and rehearsal results
- GitOps repositories and templates
- Platform documentation and handover
What we deliver
Scope is confirmed in writing in the assessment, with anything out of scope listed too.
- 01
Version upgrades
Deprecated API scans, add-on and Helm chart updates, blue/green node pools and rehearsed control-plane upgrades.
- 02
Cluster design
EKS, AKS, GKE and OKE clusters with sane networking, identity, autoscaling (Karpenter or cluster autoscaler) and multi-tenancy.
- 03
GitOps
Argo CD or Flux so every change to the cluster is reviewed and reversible.
- 04
Platform engineering
Golden paths, templates and a developer portal (such as Backstage) so teams self-serve safely.
- 05
Security
Pod security, image scanning, secrets management and policy as code.
- 06
Cost
Requests and limits, bin-packing, spot capacity and per-team cost visibility.
Fixed scope and a fixed fee, agreed in writing.
Every engagement is scoped after a free 30-minute review. The scope and fee are confirmed in writing before work starts, and the assessment fee is credited toward the project.
Step 01
Cluster upgrade readiness review
Fixed fee, scoped after the free review
Clusters, versions and support dates, deprecated API scan, add-on compatibility, upgrade plan and a fixed quote. Credited toward the upgrade.
Step 02
Upgrade or platform sprint
Fixed fee, scoped after the free review
Scoped per cluster or platform scope from the review, agreed in writing before work starts.
Samples and an example engagement
Templates with fictional systems and an illustrative scope, so you can judge the depth before the first call.
EKS clusters out of extended support
A company runs several EKS clusters on 1.31 and 1.32. Extended support costs more per cluster-hour and 1.31 extended support ends Nov 26, 2026, after which clusters are auto-upgraded.ChecklistKubernetes upgrade checklist for EKS, AKS and GKE
20 checks for deprecated APIs, add-ons, node pools and rollback before a minor-version upgrade. Printable.Sample deliverableSample assessment report: database upgrade readiness
The structure and depth of the written plan you receive at the end of a paid assessment, shown with fictional systems.From first call to delivery
You can stop after any step and keep everything we have written.
- 01
Free
Free 30-minute review
We look at what you run, what is urgent and whether a fixed-fee engagement fits. You get a short written summary.
- 02
1–2 weeks · credited
Upgrade readiness review
Inventory, API scan, plan and a fixed quote.
- 03
Typically 2–8 weeks
Upgrade or platform sprint
Rehearsed upgrades and platform work, cluster by cluster.
Technologies
Names are trademarks of their owners. Listing does not imply partnership.
Questions about this service
Straight answers on scope, fees and how we work. Anything else, ask us.
What happens when EKS extended support ends?
AWS says clusters still on the version are auto-upgraded to the oldest version in extended support. Extended support itself is billed per cluster-hour on top of the standard rate.
Can we skip Kubernetes versions?
Control planes upgrade one minor version at a time on EKS and for supported AKS clusters. The review plans the sequence and the add-on changes each step needs.
Do you support OpenShift and OKE?
Yes, alongside EKS, AKS and GKE.
Is the review fee credited?
Yes, in full, toward the upgrade if you go ahead.
Start with a free 30-minute review.
Databases, cloud or AI: talk to a senior engineer about what you run and what is coming. We reply within one business day and sign your NDA on request.
