ipv6 compatible ingress checks

[jorop]

Reference Issues or PRs

Addresses #2485
For ipv6 working, at least an update of keycloak is also necessary.

What does this implement/fix?

Ingress checks will be successful on ipv6 also using getaddrinfo instead of gethostbyname.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds a feature)
• Breaking change (fix or feature that would cause existing features not to work as expected)
• Documentation Update
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Build related changes
• Other (please describe):

Testing

• Did you test the pull request locally?
• Did you add new tests?

Any other comments?

[viniciusdc]

Hi @jorop, thank you for your contribution! We're currently in the midst of a significant update focused on our RBACs and JupyterHub, which might cause some delays in addressing your input.

We discussed this in our internal sync yesterday, and I’d like to invite you to join our community sync meetings as well: https://www.nebari.dev/docs/community/#community-meetings. These meetings are open to everyone and provide a great platform for further discussion. Please note that this item is not yet on our roadmap because we are assessing the stability of specific components that support IPv6 exclusively, which would require some more thought into it...

In the meantime, for backward compatibility, it would be beneficial to include a custom field in the ingress section of the nebari-config.yaml file. This field would allow us to toggle between different implementations as needed.

[viniciusdc]

@jorop I will be doing a check on this