Skip to content

fix(ingress): point defaultBackend at the fallback Service port - #163

Merged
aaronmgn merged 1 commit into
mainfrom
fix/fallback-ingress-port
Aug 5, 2026
Merged

fix(ingress): point defaultBackend at the fallback Service port#163
aaronmgn merged 1 commit into
mainfrom
fix/fallback-ingress-port

Conversation

@aaronmgn

@aaronmgn aaronmgn commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Summary

The Ingress defaultBackend points 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: change spec.defaultBackend.service.port.number from 3000 to 80. An Ingress backend uses a Service port. The fallback Service publishes port 80 and sends traffic to container port 3000, so 3000 does not resolve.
  • charts/graylog/tests/fallback_test.yaml: three new tests. The first shows that the fallback Service publishes 80 and targets 3000. The second shows that defaultBackend uses 80. The third shows that defaultBackend is 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.

  • Tests added/updated
  • Documentation updated
  • This PR includes a new feature
  • This PR includes a bugfix
  • This PR includes a refactor

Testing Checklist

Static Validation

  • Linter check passes: helm lint ./charts/graylog
  • Helm renders local template sucessfully: helm template graylog ./charts/graylog --validate

--validate needs the MongoDB Operator CRD. The test cluster does not have it. helm template without --validate passes.

Installation

  • Fresh installation completes successfully: helm install graylog ./charts/graylog
  • All pods reach Running state: kubectl rollout status statefulset/graylog
  • Helm tests pass: helm test graylog

Functional (if applicable)

  • Web UI accessible and login works
  • DataNodes visible in System > Cluster Configuration
  • Inputs can be created and receive data

Upgrade (if applicable)

  • Upgrade from previous release succeeds
  • Scaling up/down works correctly
  • Configuration changes apply correctly

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 unittest passes: 335 tests in 28 suites, up from 332.
  • The new test finds the fault. With number: 3000 back in place, the test "Ingress defaultBackend targets the fallback Service port, not the container port" fails. The other nine pass.

Notes for reviewers

  • Verify all applicable tests above pass
  • Validate that the linked issues are no longer reproducible, if applicable
  • Sync up with the author before merging
  • The commit history should be preserved - use rebase-merge or standard merge options when applicable

A named Service port can prevent this class of fault. That changes the rendered Service, so this PR keeps the small numeric fix.

@aaronmgn
aaronmgn requested a review from alix-graylog August 5, 2026 00:44
@aaronmgn aaronmgn self-assigned this Aug 5, 2026
@aaronmgn
aaronmgn merged commit 91bee91 into main Aug 5, 2026
9 checks passed
@aaronmgn
aaronmgn deleted the fix/fallback-ingress-port branch August 5, 2026 15:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants