Support ipv6 for server in ipv6-only kubernetes cluster

[aldo-airtm]

What type of PR is this?

• Bug Fix

Description

The listener address is hardcoded to IPv4-only (0.0.0.0) which breaks in an IPv6-only host. gunicorn supports the [::] host as a dualstack wildcard, so that's what I'm changing here.

How is this tested?

• Unit tests (pytest, jest)
• E2E Tests (Cypress)
• Manually
• N/A

Built the docker image locally and started it

[aldo-airtm]

Reopening PR #7589

[cubic-dev-ai]

No issues found across 1 file

[aldo-airtm]

In a dual-stack environment, both 0.0.0.0 and [::] work for both v4 and v6, but in a v6-only system, only [::] works properly.

[eradman]

In a dual-stack environment, both 0.0.0.0 and [::] work for both v4 and v6, but in a v6-only system, only [::] works properly.

Do you mean that IPv4 is disabled, or that routing for IPv4 addresses are not assigned?

[aldo-airtm]

Do you mean that IPv4 is disabled, or that routing for IPv4 addresses are not assigned?

IPv4 is disabled at the host level

[eradman]

This does solve the problem when running single-stack IPv6

$ host redash.default.svc.mykube.lan
redash.default.svc.mykube.lan has IPv6 address fd00:f4:2::c

Tested on kubernetes using

---
apiVersion: v1
kind: Service
metadata:
  name: redash
spec:
  clusterIP: None
  ports:
  - port: 5000
    targetPort: 5000
  selector:
    app: redash
  ipFamilyPolicy: SingleStack
  ipFamilies:
  - IPv6

Also confirmed that this is still compatible with IPv4.
Thank you @aldo-airtm!

[eradman]

@aldo-airtm please try rebasing this change and pushing agin