Free online Kubernetes Gateway API and HTTPRoute manifest generator. Visually construct GatewayClass, Gateway listeners, and HTTPRoute routing rules conforming to official SIG Gateway API gateway.networking.k8s.io/v1 specifications. Supports weighted canary deployments, TLS termination, header modifications, HTTP redirects, URL rewrites, request mirroring, and multi-tenant cross-namespace attachment.
Build production-ready Gateway, Listener, and HTTPRoute specs with canary weighting, request filters, and cross-namespace routing.
Generated manifests conform to the official SIG Gateway API gateway.networking.k8s.io/v1 standard, compatible with NGINX Gateway Fabric, Istio, Cilium, Envoy Gateway, Traefik, and GKE.
Specify the Gateway resource name, target Kubernetes namespace, and GatewayClassName controller implementation (such as NGINX Gateway Fabric, Istio, Cilium, Envoy Gateway, Traefik, or GKE).
Add HTTP, HTTPS, TLS, or gRPC listeners with custom port bindings, hostname wildcards, TLS secret references, and cross-namespace allowedRoutes policies.
Configure HTTPRoute metadata and attach it to parent Gateways. Define path matchers (PathPrefix, Exact, Regex), header filters, and method controls.
Set up proportional backendRef traffic weights (e.g. 90% stable / 10% canary), header modifiers (set/add/remove), HTTP redirects, URL rewrites, or shadow request mirroring.
One-click load enterprise patterns including 'HTTPS TLS Redirect', 'Canary 90/10 Split', 'Microservices Path Router', 'A/B Header Routing', or 'Multi-Tenant Cross-Namespace Attachment'.
Preview live multi-document YAML manifests (separated by '---'), copy to clipboard, download .yaml files, or copy equivalent kubectl CLI installation commands.
Split incoming web traffic proportionally between stable v1 and experimental v2 deployments using weighted backendRefs without changing DNS or ingress controllers.
Allow central platform infrastructure teams to own root Gateways in system namespaces while enabling application teams to attach HTTPRoutes from tenant namespaces.
Instantiate edge edge-listeners that automatically catch cleartext port 80 traffic and issue HTTP 301 Permanent Redirects to encrypted TLS port 443 listeners.
Route incoming HTTP requests containing specific headers (such as X-Beta-Tester: true) or cookies to dedicated experimental microservice pods.
Safely duplicate real production API traffic and mirror it asynchronously to a staging or shadow service without affecting production client latency.
gateway.networking.k8s.io/v1)In modern cloud-native Kubernetes infrastructures, managing external ingress traffic, API gateway routing, and service-to-service communication requires a flexible, role-oriented API. For over a decade, the legacy Kubernetes Ingress API (networking.k8s.io/v1) served as the standard mechanism for exposing HTTP services. However, as microservice architectures grew, legacy Ingress suffered from fundamental limitations: vendor-specific annotations (nginx.ingress.kubernetes.io/*), lack of cross-namespace delegation, rigid routing rules, and single-resource ownership contention.
To overcome these architectural constraints, the Kubernetes Special Interest Group (SIG-Network) developed the Kubernetes Gateway API (gateway.networking.k8s.io/v1). The Gateway API is an open, extensible, role-oriented standard designed to govern layer 4 (TCP/UDP) and layer 7 (HTTP/gRPC) routing in Kubernetes. Our Kubernetes Gateway API & HTTPRoute Builder provides a client-side visual environment for architecting, validating, and generating production-ready Gateway and HTTPRoute v1 manifests and kubectl terminal commands.
Ingress file. Gateway API decouples infrastructure configuration (GatewayClass & Gateway) from application routing rules (HTTPRoute).HTTPRoute resources inside their isolated tenant namespaces and safely attach them to a central Gateway managed by platform engineering.backendRefs), request header modification, URL rewrites, and traffic mirroring are standardized natively in the spec without relying on custom vendor annotations.HTTP, HTTPS, gRPC, TLS, TCP, and UDP protocols.| Architectural Feature | Legacy Ingress (networking.k8s.io/v1) | Gateway API (gateway.networking.k8s.io/v1) |
|---|---|---|
| API Maturity Standard | Legacy Maintenance Mode | Active Production Standard (GA v1.1+) |
| Role Separation | Single monolithic file | Decoupled: GatewayClass, Gateway, HTTPRoute |
| Cross-Namespace Support | Impossible (strictly single namespace) | Native via parentRefs & allowedRoutes |
| Weighted Traffic Splitting | Vendor Annotations (e.g. NGINX canary annotation) | Native weight field on backendRefs |
| Header Modification | Vendor Annotations | Native RequestHeaderModifier filter |
| HTTP Redirects & Rewrites | Vendor Annotations | Native RequestRedirect & URLRewrite filters |
| Traffic Shadowing / Mirror | Vendor Annotations | Native RequestMirror filter |
| gRPC Protocol Support | Custom annotations / CRDs | Native GRPCRoute CRD support |
GatewayClass (Infrastructure Engine)GatewayClass defines the controller implementation that synthesizes gateway resources into physical network load balancers, reverse proxies, or service mesh proxies.
Gateway (Network Entry Point & Security Guard)Gateway instances define network endpoints (IP addresses or hostnames) and listeners bound to specific ports. Listeners define which protocols are accepted and which certificates are presented.
HTTPRoute (Application Routing & Traffic Policy)HTTPRoute resources define how incoming HTTP requests matching specific criteria (hostnames, paths, headers, query parameters) are filtered, modified, and forwarded to backend Service endpoints.
legacy-ingress.yaml):k8s-gateway-api-full.yaml):Deploying production-grade Gateway API controllers requires adherence to enterprise security benchmarks:
from: All) unless necessary. Use from: Same or from: Selector with strict label namespaces to prevent unauthorized teams from attaching malicious HTTPRoutes to production hostnames.cert-manager.io to automatically issue Let's Encrypt or private CA TLS certificates for Gateway certificateRefs.RequestRedirect filters to HTTPS port 443 to eliminate plaintext data transmission.Accepted: True, Programmed: True) to detect unattached or rejected HTTPRoutes across tenant namespaces:Create production Kubernetes Deployment, Service, Ingress, ConfigMap, and Secret manifests.
Visually build and validate production-ready Kubernetes NetworkPolicy manifests to enforce Zero-Trust microservice isolation, pod ingress/egress filtering, and CIDR ipBlock rules.
Free online client-side tool to generate Kubernetes ConfigMap and Secret manifests (Opaque, TLS, Docker Registry) with automatic Base64 encoding, .env parsing, and CLI commands.
Free online visual Kubernetes RBAC generator to build Roles, ClusterRoles, ServiceAccounts, and RoleBindings with fine-grained API permissions and CLI commands.
Calculate Pod CPU & Memory requests/limits, estimate cluster node capacity requirements, determine QoS classes, and generate ResourceQuota & Helm YAML manifests.