[gateway] new chart to deploy Gateway resource with optional cert-manager certificate #189
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
DanielRaapDev
changed the title
philippwiesner
approved these changes
Jul 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This helm chart deploys a Gateway resource to create load balancer infrastructure for ingress traffic. It can optionally retrieve certificates for the domains by using the cert-manager to retrieve Let's Encrypt certificates for TLS.
The design goal of this chart is that a single Gateway exists for the whole Kubernetes cluster. So it is expected to be deployed in its own namespace. The services to be made available with HTTPRoutes must reside in the namespace of the service and reference this gateway. So we have a distributed setup.