Repository navigation
Remove nginx ingress controller. - #332
Merged
Merged
Conversation
majst01
reviewed
Sep 10, 2026
Comment on lines
+69
to
+70
| | 80 | 172.42.0.42 | HTTP ingress | | ||
| | 443 | 172.42.0.42 | HTTPS ingress | |
Contributor
Author
There was a problem hiding this comment.
I think it still can be called ingress. The term should be independent how this is implemented in Kubernetes.
majst01
approved these changes
Sep 10, 2026
8 tasks
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
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.
Description
Now that we migrated everything to Gateway API, we can remove ingress nginx.
Used AI-Tools ✨