Browse categories
Explore
Fiverr Pro
English
$
USD
I will migrate ingress nginx to gateway API on your kubernetes cluster
Cloud Infrastructure Architect, Kubernetes Expert, AWS Certified
Software Architect with 13+ years of experience specializing in cloud infrastructure, containerization, and Kubernetes orchestration. AWS Certified DevOps Engineer and CNCF Certified Kubernetes Applic...
About this Gig
Ingress NGINX has been retired by the upstream Kubernetes project. It still runs but it no longer receives bug fixes or security patches. If it's in your cluster, you are running unpatched internet-facing infrastructure.
There is no drop-in replacement. Gateway API is a different resource model, and a copy-paste migration will drop traffic.
I migrate production clusters off Ingress NGINX without downtime.
What you get:
- Full inventory of every Ingress resource, annotation and custom snippet in use
- Mapping of each one to its Gateway API equivalent, and a flag on anything with no equivalent
- Controller recommendation for your setup (Envoy Gateway, NGINX Gateway Fabric, or cloud-native)
- Parallel-run cutover plan so old and new paths serve traffic together before you switch
- TLS, cert-manager, external-dns and WAF continuity checked
I work read-only first. You get the assessment before anyone touches a manifest.
Platforms: EKS, GKE, AKS, self-managed, k3s.
Message me with your cluster version and rough Ingress count for a fixed quote.
Tools:
Kubernetes
•
OpenShift
•
Amazon EKS
Frameworks:
Terraform
•
Pulumi
Programming language:
Bash
•
Python
•
PowerShell
Expertise:
Migration
•
Configuration
FAQ
Can't I just switch the ingressClass?
No. Gateway API uses different resources (Gateway, HTTPRoute) and most NGINX annotations have no direct equivalent. That mapping is the actual work.
Do you need admin access?
Not for the audit — read-only only. Write access is only needed if you buy a migration package, and it can be scoped to specific namespaces.
Will there be downtime?
No. I run both paths in parallel and shift traffic gradually, so rollback is instant.
What if we'd rather move to a different controller than Gateway API?
Fine — the audit covers third-party controller options too and recommends based on what your annotations actually need.
We're on an old cluster version, can you help?
Yes, please check our other gig for kubernetes version migration. That will have separate charges.
