Browse categories
Explore
Fiverr Pro
English
$
USD
I will migrate your ingress nginx to kubernetes gateway API
About this Gig
Ingress NGINX is being retired, and many production clusters need a safe migration path. I will migrate your current Kubernetes Ingress setup (ingress-nginx) to the modern Gateway API (Gateway + HTTPRoute) with a focus on reliability, security, and minimal downtime.
What you get
- Migration plan tailored to your cluster (on-prem)
- Gateway API manifests (GatewayClass/Gateway/HTTPRoute) aligned with your routing needs
- TLS/HTTPS setup (cert-manager compatible if applicable)
- Rewrite/redirect/headers support (where supported by your chosen controller)
- Validation checklist
- Clean documentation so your team can maintain it
Important
- Gateway API is an API spec; the implementation depends on the controller (e.g., Envoy Gateway, Istio, Kong, HAProxy, NGINX Gateway). I will recommend the best option for your environment and constraints.
- Snippet-heavy Ingress configs may require refactoring (Ill flag risks early).
Message me before ordering if you have complex rules, custom annotations, or multi-tenant clusters.
Tools:
Kubernetes
•
Docker
Frameworks:
Npm
•
Ansible
Cloud Provider:
Other
Programming language:
Python
•
Java
•
JavaScript
•
Bash
Expertise:
Installation
•
Migration
•
Configuration
Other DevOps Engineering Services I Offer
FAQ
Why are your prices structured this way?
My Basic package is an assessment + migration plan (low-risk entry). Standard/Premium include implementation work and validation. Larger setups are priced fairly via “additional Ingress” extras or a custom offer.
What’s included vs. not included?
Included: Gateway API manifests, routing/TLS mapping (as applicable), validation checklist, and handover notes. Not included by default: full cluster administration, application debugging, or enterprise-only features unless agreed in advance.
What if I have more than the package limit (Ingress/resources)?
No problem. Add the “Additional Ingress” extras or message me for a custom offer. This keeps the base packages affordable while scaling for bigger projects.
Do you need cluster access?
For Basic, exported YAML manifests are enough. For implementation (Standard/Premium), I typically need a kubeconfig with the minimum required permissions (or a guided session).
Can you guarantee zero downtime?
I aim for minimal downtime using staged rollout and safe cutover. “Zero downtime” depends on your LB/DNS setup and production constraints. I’ll confirm the best approach during the assessment.
