1. What is the nature and description of the request?

The telco customer is using Openshift IPv6 and IPv4 dual stack with IPv6 as primary and when they tried to deploy eda with AAP 2.4 on OCP 4.16, the eda-api pod will not be ready due to the health check failure.
It is found in AAP 2.4 on OCP, eda-api pod cannot be successfully deployed due to listener binding only to IPv4 .

_{Containers:
  eda-api:
    Container ID: cri-o://f2c58e8fd63effcc794062d77d714316c355897ec04135fcebd0d9328929c1f6
    Image: registry.redhat.io/ansible-automation-platform-24/eda-controller-rhel8@sha256:1441881680eb208d99183d9730486d9e59c2298d687fbd4e44340a63bac4fa88
    Image ID: registry.redhat.io/ansible-automation-platform-24/eda-controller-rhel8@sha256:1441881680eb208d99183d9730486d9e59c2298d687fbd4e44340a63bac4fa88
    Port: 8000/TCP
    Host Port: 0/TCP
    Args:
      /bin/bash
      -c
      gunicorn --bind 0.0.0.0:8000 --workers 2 aap_eda.wsgi:application　　　　★}

Customer requests that Dual Stack with IPv6 primary support eda component and the feature be launched in the first half of 2025 better in AAP 2.5 on OCP but AAP 2.4 can also be acceptable.

2. Why does the customer need this? (List the business requirements here)

Telco customer is working to move from IPv4 to IPv6 slightly, and IPv4/v6 dual stack is a mandatory requirement now.

EDA enables telco customer to automate responses to network events or incidents in real time. This is crucial for large, dynamic environments where manual intervention would be too slow or error-prone.

3. How would you like to achieve this? (List the functional requirements here)

IPv6 should be supportable(installation and operations) in eda component of AAP 2.4 as operator on OCP .

4. List any affected known dependencies: Doc, UI etc..

https://issues.redhat.com/browse/ANSTRAT-1380

5. Github Link if any