-
Notifications
You must be signed in to change notification settings - Fork 230
Open
Labels
kind/bugSomething isn't workingSomething isn't workingpriority/normalAn issue with the product; fix when possibleAn issue with the product; fix when possibleuntriagedIndicates the newly create issue has not been triaged yetIndicates the newly create issue has not been triaged yet
Description
Is there an existing issue for this?
- I have searched the existing issues
Deploy type
Downstream version (eg. OpenShift AI 2.4
)
Version
2.13.1
Current Behavior
The ODH Dashboard backend encounters two critical issues when deployed in an IPv6-only environment:
-
Readiness/Liveness Probe Fails:
The server binds only to0.0.0.0
(IPv4), which causes connection failures when the liveness probe attempts to connect to an IPv6 address. -
Hostname/IP Validation Failure:
The backend throws errors due to improper handling of IPv6 addresses in API requests, specifically missing brackets around IPv6 addresses in URLs.
Expected Behavior
- The backend should bind to an IPv6-compatible address (
::
) or dynamically detect the appropriate interface. - IPv6 addresses in API requests should be enclosed in square brackets (
[]
) to avoid hostname validation issues.
Steps To Reproduce
- Deploy the ODH Dashboard in an IPv6-only OpenShift cluster.
- Observe the following error in the Kubernetes event logs:
Liveness probe failed: dial tcp [fd02:0:0:1::13c]:8080: connect: connection refused - Observe the following error in the backend logs:
Hostname/IP does not match certificate's altnames: Host: fd02. is not in the cert's altnames
Workaround (if any)
No response
What browsers are you seeing the problem on?
No response
Anything else
No response
Metadata
Metadata
Assignees
Labels
kind/bugSomething isn't workingSomething isn't workingpriority/normalAn issue with the product; fix when possibleAn issue with the product; fix when possibleuntriagedIndicates the newly create issue has not been triaged yetIndicates the newly create issue has not been triaged yet