Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trow unreachable over IPv6 #333

Open
YannikSc opened this issue Dec 10, 2022 · 2 comments
Open

Trow unreachable over IPv6 #333

YannikSc opened this issue Dec 10, 2022 · 2 comments

Comments

@YannikSc
Copy link
Contributor

Describe the bug

When running a cluster with DualStack/IPv6 trow is not reachable as it only listens on 0.0.0.0 (all IPv4 interfaces).

This could be mitigated by letting Trow/Rocket listen by default on :: (actually all interfaces IPv4 and IPv6).

Another workaround would be to allow the helm chart to set the --host flag.

To Reproduce

  • Setup a cluster with IPv6 support
  • Setup an ingress controller with IPv6 support
  • Setup trow ingress (or IPv6 service)

Expected behavior

Trow is reachable at the configured domain through the ingress/directly via IPv6

Trow Info

  • Install method: Helm
  • Helm Chart info:
apiVersion: v2
appVersion: 0.3.5
description: Helm chart for Trow registry
name: trow
type: application
version: 0.3.5 

Kubernetes

  • Kubernetes distro/host: kubeadm on Arch
  • Kubernetes version: v1.25.5
  • Container Runtime: ContainerD
@awoimbee
Copy link
Collaborator

Note that Trow uses Rocket, which does not support listening to multiple addresses in a single instance. The workaround described here might work tho: rwf2/Rocket#1581.
Otherwise the solution is to have multiple instances of rocket running (like I did here).

@amouat
Copy link
Contributor

amouat commented Dec 22, 2022

Thanks @awoimbee !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants