feat: Migrate from ingress-nginx to Kubernetes Gateway API #1486
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
skrobul
changed the title
skrobul
force-pushed
the
gateway-api
branch
2 times, most recently
from
703b2c6 to
cd454e1
Compare
cardoe
reviewed
Dec 12, 2025
Contributor
cardoe
left a comment
cardoe
left a comment
There was a problem hiding this comment.
Looks good. Just one question.
components/envoy-gateway/values.yaml
Outdated
| enableEnvoyPatchPolicy: true | ||
| logging: | ||
| level: | ||
| default: debug |
Contributor
There was a problem hiding this comment.
Do we want to ship the default as debug?
Collaborator
Author
There was a problem hiding this comment.
This has been changed in later commit (5d5b911)
We no longer do "static" install of the cert-manager, because custom configuration needs to be provided to enable the Gateway API functionality.
Includes cert-manager integration.
For HTTPRoute, if the name is not explicitly set, default to first part of the hostname/FQDN.
Technically, this gives user a way to configure which routes is the listener going to accept.
Some of the services require passthrough TLS instead of termination.
This adds ability to direct traffic over https without doing cert verification.
So that we can disable TLS validation...
These have been replaced by HTTPRoutes
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR migrates UnderStack from the legacy Ingress API with ingress-nginx controller to the Kubernetes Gateway API with Envoy Gateway. This migration is necessary due to the ingress-nginx project retirement with a March 2026 deadline.
Motivation
Changes
Infrastructure Components
Envoy Gateway Deployment (
components/envoy-gateway/)apps/infra/envoy-gateway.yamlenvoy-configs Helm Chart (
components/envoy-configs/)cert-manager Updates
enableGatewayApi: trueOpenStack Helm Charts
Updated all OpenStack service components to disable Ingress generation:
network.use_external_ingress_controller: truemanifests.ingress_api: falsemanifests.service_ingress_api: falseApplication Updates
ArgoCD, Argo Workflows, Dex
external-dns
Architecture
The new architecture uses:
envoy-gatewaynamespaceenvoy-configs.yamlDocumentation
Migration Path for Deployments
Existing deployments need to update their
deploy/<site>/repository:skip: truefor ingress-nginx inapps.yamlmanifests/envoy-gateway/helm-configs/envoy-configs.yamlwith Gateway and route definitionsSee
docs/operator-guide/gateway-api.mdfor detailed instructions.Breaking Changes
Deployments must update their site-specific configuration to:
helm-configs/envoy-configs.yamlRelated Links