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.

Sign up for GitHub

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

Jump to bottom

dns-lookup-family: default to v4 preferred #522

Open
desimone opened this issue Feb 13, 2023 · 2 comments
Open

dns-lookup-family: default to v4 preferred #522

desimone opened this issue Feb 13, 2023 · 2 comments
Assignees
@wasaga
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. NeedsMoreData Waiting for additional user feedback or case studies

Comments

@desimone
Copy link

Originally posted by @calebdoxsey in pomerium/pomerium#3954 (comment)
@wasaga
Copy link
Collaborator

wasaga commented Apr 20, 2023 •
edited
Loading

I think it may stay in backlog for a bit longer.

  1. previously, most Kubernetes clusters were IPv4 only so it did not really had any meaning.
  2. core uses IPv4_PREFERRED by default now, which basically implements this ticket
  3. dual-stack IPv4/IPv6 k8s clusters are just starting to appear; and by spec, the Pod would always have both
  4. I do not want to pollute the CRD definition with this rather esoteric option. if we add it eventually, it should probably go to runtime arguments.

@desimone desimone added NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. NeedsMoreData Waiting for additional user feedback or case studies labels Apr 20, 2023
@vinc0u
Copy link

vinc0u commented May 21, 2024

Hello,
a lot of ipv6 only clusters are starting to appear. As we are currently ipv6 only core we are hit by this issue. I would love to contribute.
What about an argument as in java --prefer-ipv4-stack=false that would default to true if not set. I can help mainly in testing and a bit in development

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wasaga wasaga

Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. NeedsMoreData Waiting for additional user feedback or case studies
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@wasaga @desimone @vinc0u