Webservice: Enable IPv6 binding by default
What does this MR do?
Re-enables IPv6 binding for Puma by default, now that the IPv4 fallback has been implemented in the webservice container.
The fallback was added in gitlab-org/build/CNG!3018 (merged), which ensures Puma gracefully falls back to IPv4 when IPv6 localhost binds are unavailable. This prevents the Cannot assign requested address - bind(2) for "::1" error that caused previous reverts in !4072 (merged) and !5151 (merged).
This change makes the chart work out of the box on IPv4-only, IPv6-only, and dual-stack clusters.
Changelog: changed
Closes #6567 (closed)
Related issues
Closes #6567 (closed)
Test instructions
Testing this can be tricky as it's influenced by kernel settings. One common K8s distro where IPv6 was not bindable was GKE, which we confirmed to be working in gitlab-org/build/CNG!3018 (merged).
Author checklist
For general guidance, please follow our Contributing guide.
Required
For anything in this list which will not be completed, please provide a reason in the MR discussion.
- Merge Request Title and Description are up to date, accurate, and descriptive.
- MR targeting the appropriate branch.
- MR has a green pipeline.
- Documentation created/updated.
- Tests added/updated.
- Have you validated that your change works end-to-end on a real cluster deployment?
- Describe how you did it in a comment.
-
Equivalent MR/issue foromnibus-gitlabopened.
Reviewers checklist
- MR has a green pipeline on https://gitlab.com/gitlab-org/charts/gitlab.
- Consider downstream impact to the Operator, as per evaluating impact from changes to GitLab chart.