Actions
Issue #5414
closed
Story #5132: [Epic] As a user, I can consume Pulp 3 from OperatorHub.io
HTTP requests to containers hang over IPv6
Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
Operator - Moved to Github Issues
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
Our individual Pulp containers providing Kubernetes external services (pulp-api & pulp-content) listen on only IPv4.
However, Kubernetes will forward both IPv4 and IPv6 often. Such as on Fedora 30 with k3s. An IPv6 connection will hang.
And many clients will prefer IPv6 over IPv4, including a Fedora 30 host connecting to "localhost".
This is observed during the development of the demo pulp install script (#5375):
https://github.com/mikedep333/Vagrantfiles/blob/master/pulp-insta-demo.sh
Related issues
Actions
.
Problem: HTTP requests to containers hang over IPv6
Solution: Bind to IPv6, and thus impliclty IPv4. This implicit listen can reliably happen in containers because of network namespaces.
Also, standardize container script syntax.
Fixes: #5414 HTTP requests to containers hang over IPv6 https://pulp.plan.io/issues/5414
re: #5375 As a user, I can use a single script to install k3s and launch pulp-operator https://pulp.plan.io/issues/5375
[noissue]