[bitnami/haproxy] Add support for ipFamilyPolicy and ipFamilies service parameters

[I501307]

Name and Version

bitnami/haproxy (all versions)

What steps will reproduce the bug?

Name and Version
bitnami/haproxy (all versions)

What is the problem this feature will solve?
The HAProxy Helm chart does not support configuring ipFamilyPolicy and ipFamilies for the Service resource, making it impossible to deploy in dual-stack IPv4/IPv6 Kubernetes clusters. The service defaults to single-stack IPv4, which causes
connectivity issues in IPv6-primary clusters.

What is the feature you are proposing to solve the problem?
Add service.ipFamilyPolicy and service.ipFamilies parameters to the values.yaml and update the service template to use them, similar to how other Bitnami charts are being updated (see #24531 for elasticsearch).

What alternatives have you considered?

• Using post-renderers (not available in all deployment platforms like Landscaper)
• Forking the chart (maintenance burden)

Additional context
Bitnami mentioned in #24531 (elasticsearch) that they created an internal task to add IP families support to all charts in the catalog. It would be great to include HAProxy in this effort.

Related issues:

• [bitnami/elasticsearch] in Dualstack IPv6 & SVC mismatch #24531 (elasticsearch)
• [bitnami/mariadb-galera] Support IPv6 Deployment #21956 (mariadb-galera)

[carrodher]

Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.

Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.

[I501307]

Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.

Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.

@carrodher mira mira 👀!

PR is ready: #36385

Context: This is blocking our production deployments in dual-stack Kubernetes clusters. We're currently stuck using fragile post-renderer workarounds that aren't compatible with our deployment tooling (Landscaper).

The changes are minimal and follow the existing pattern from elasticsearch/mariadb-galera charts. Could you prioritize reviewing this? We're under time pressure to ship IPv6 support across our infrastructure.

Let me know if any changes are needed - happy to iterate quickly! 🚀

[carrodher]

Thank you for opening this issue and submitting the associated Pull Request. Our team will review and provide feedback. Once the PR is merged, the issue will automatically close.

Your contribution is greatly appreciated!