Key capabilities
- Process inputs locally without connecting to a cluster
- Start with a sample and review each result
- Explain modeled rules and unsupported behavior
- Export reviewable configuration and analysis
Ingress to Gateway API Migration & Validator
Convert Ingress v1 to Gateway and HTTPRoute drafts, resolve named Service ports, inspect routing references and test request matching without contacting a cluster.
Your configuration stays in this browser
No cluster access, kubectl execution or configuration uploads. Anonymous operation events contain only operation types and size/time buckets, never input values.
Enter the name of a GatewayClass already installed in the target cluster. It is not inferred from ingressClassName.
Up to 1 MiB and 300 Kubernetes objects. YAML, JSON and Kubernetes Lists are supported.
Start with a sample or enter your configuration, then run the tool.
Model boundaries
Migrates portable networking.k8s.io/v1 Service backends, Exact/Prefix paths and TLS references. Controller annotations, regex paths, auth, rate limits and redirects are never silently translated. TLS certificates, GatewayClass availability, cross-namespace grants, status conditions and live traffic require target-cluster verification. Validation is a supported-rule check, not full CRD schema validation.
About Ingress to Gateway API Migration & Validator
Convert portable routing rules and identify migration gaps. Convert Ingress v1 to Gateway and HTTPRoute drafts, resolve named Service ports, inspect routing references and test request matching without contacting a cluster. The core workflow is designed to run in your current browser.
Useful for
- Review a proposed configuration before applying it
- Understand a result using a reproducible offline example
Frequently asked questions
Is Ingress to Gateway API Migration & Validator free to use online?
Yes. Ingress to Gateway API Migration & Validator opens in a modern browser and does not require desktop software installation.
What is Ingress to Gateway API Migration & Validator useful for?
Common use cases include Review a proposed configuration before applying it; Understand a result using a reproducible offline example.
Is my input or file uploaded?
The core processing workflow is designed to run locally in the browser. Key capabilities include Process inputs locally without connecting to a cluster, Start with a sample and review each result, Explain modeled rules and unsupported behavior; account, comments, and anonymous analytics may still create normal site requests.
Comments
0 comments
AAccount
Sign in to comment and reply.
No comments yet. Be the first to leave feedback.