fix(ingress): point defaultBackend at the fallback Service port - #163
Merged
Conversation
22 tasks
alix-graylog
approved these changes
Aug 5, 2026
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.
Summary
The Ingress
defaultBackendpoints at the container port of the fallback, not at its Service port. The waiting room never answers.Details
charts/graylog/templates/service/ingress/graylog.yaml: changespec.defaultBackend.service.port.numberfrom3000to80. An Ingress backend uses a Service port. The fallback Service publishes port80and sends traffic to container port3000, so3000does not resolve.charts/graylog/tests/fallback_test.yaml: three new tests. The first shows that the fallback Service publishes80and targets3000. The second shows thatdefaultBackenduses80. The third shows thatdefaultBackendis absent when the waiting room is off.The waiting room is on by default when ingress is on. This fault is on the default ingress path.
Linked issues
None.
PR Checklist
Please check the items that apply to your change.
Testing Checklist
Static Validation
helm lint ./charts/grayloghelm template graylog ./charts/graylog --validate--validateneeds the MongoDB Operator CRD. The test cluster does not have it.helm templatewithout--validatepasses.Installation
helm install graylog ./charts/graylogkubectl rollout status statefulset/grayloghelm test graylogFunctional (if applicable)
Upgrade (if applicable)
The installation and functional tests did not run. A test of the waiting room needs a cluster with an nginx Ingress controller.
Specific to this PR
helm unittestpasses: 335 tests in 28 suites, up from 332.number: 3000back in place, the test "Ingress defaultBackend targets the fallback Service port, not the container port" fails. The other nine pass.Notes for reviewers
A named Service port can prevent this class of fault. That changes the rendered Service, so this PR keeps the small numeric fix.