You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(infrastructure): migrate application exposure from Ingress to Gateway API
The `application` template's exposure layer now emits
gateway.networking.k8s.io/v1 HTTPRoutes instead of networking.k8s.io/v1
Ingress objects.
- Template: two HTTPRoutes (one always, one /api-only in mode=none) attach
to a platform Gateway via parentRefs; status reads from httpRoute.hostnames.
- Token seam: ${kedge.ingressClass} -> ${kedge.gatewayName} +
${kedge.gatewayNamespace}; env KEDGE_INGRESS_CLASS -> KEDGE_GATEWAY_NAME /
KEDGE_GATEWAY_NAMESPACE. Defaults point at the cfgate Cloudflare Tunnel
Gateway (cloudflare-tunnel / cfgate-system).
- ApplicationSpec.IngressClass -> ApplicationSpec.Gateway (GatewayRef);
regenerated deepcopy + CRDs; chart values/deployment/operator-config;
Makefile dev target; tests; provider doc + README.
sandbox-runner is unchanged (no Ingress; preview goes via the k8s service
proxy). Foundation for issue #351 (Core Kedge Gateway Endpoint broker).
Bundles unrelated in-flight working-tree changes: kedge-hub HTTPRoute
chart template + values, hub bootstrap tweak, provider portal bundles,
and local .claude settings.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
run-provider-infrastructure-operator: build-infrastructure-provider ## Run the infrastructure provider in OPERATOR mode (bootstrap reconcile + serve from a provider + runtime kubeconfig)
0 commit comments