Comments (11)
Hi @olix0r,
I don't have follow any docs about that but I wrote a detailed blog post about that,
https://opsnotice.xyz/kubernetes-ipv6-only/
I will continu to try too in my cluster to report any problem ;)
Thanks !
from linkerd2.
Thanks for this report! It's important to us that Conduit support things like IPv6 out-of-the-box.
Can you share any pointers/references/docs on how you've set up your kubernetes cluster to use IPv6? I'd like to replicate this environment for integration tests.
from linkerd2.
Like @olix0r said, we definitely want to support IPv6-only configurations. I believe there's only one place where we use DNS in Conduit: resolving the hostname of the control plane. Until we find out what the issue is with that, you may be able to work around this by allocating an IPv4 address only to the control plane pods.
#257 was filed as a duplicate of this, which may mean there's more interest in IPv6-only configurations than we expected, so we should consider increasing the priority.
from linkerd2.
Hi,
Sorry for opened two issue, I forgot about the first one lol,
Yeah, conduit seem really a great product and I really looking forward about trying this with my production services in IPv6 cluster and more since you support HTTP1.1 and TCP stuffs.
I can support you on the testing side if you release some test image, I can try them quickly if needed ;)
from linkerd2.
IPv6 support is currently unprioritized, but contributions are welcome! Specific error reports around breakages due to IPv6 also welcome.
from linkerd2.
I gived a new try on v0.4.0 release,
I don't get any error on the Conduit deployment,
But when I deploy my Nginx deployment with conduit-proxy, here is the logs :
INFO conduit_proxy using controller at HostAndPort { host: DnsName(Name(Name("proxy-api.conduit.svc.k8s.my-cluster.tld"))), port: 8086 }
INFO conduit_proxy routing on V4(127.0.0.1:4140)
INFO conduit_proxy proxying on V4(0.0.0.0:4143) to None
INFO conduit_proxy serving Prometheus metrics on V4(0.0.0.0:4191)
INFO conduit_proxy protocol detection disabled for inbound ports {25, 3306}
INFO conduit_proxy protocol detection disabled for outbound ports {25, 3306}
ERR! conduit_proxy::control "controller-client", controller error: Error attempting to establish underlying session layer: DNS resolution failed
If it can help ! 😄
from linkerd2.
@valentin2105 thanks for the updated information! i think we're getting closer to being able to fix this. as we improve some of the discovery logic for 0.5, we can take a look trying to determine what has to change in the proxy to accommodate this.
from linkerd2.
@olix0r Thanks for investigating this,
Looking forward seen conduit running at glance on IPv6 ;)
from linkerd2.
This is most likely due to limitations of the abstract_ns/ns_dns_tokio crates. In particular, note things like https://github.com/tailhook/abstract-ns/blob/af4fa2abe1aed67c505364cc78aaf2e7dd5fcb10/ns-dns-tokio/src/lib.rs#L72-L81 where AAAA support just wasn't considered yet.
I think we'll have to switch to another crate--probably Trust-DNS--to fix this.
from linkerd2.
@briansmith TrustDNS seem really better and support IPv6.
Pretty strange for a DNS library to support only IPv4..
from linkerd2.
Tracking IPv6 support in #3849.
from linkerd2.
Related Issues (20)
- Enable OpenSSF Scorecard to enhance security practices across the project HOT 2
- "Operation not permitted" error in linkerd-proxy on edge-24.6.4 HOT 12
- Better documentation on the expectations for `networkValidator.connectAddr` for `linkerd-control-plane` helm chart values HOT 4
- Linkerd Destination Pod Unhealthy Warnings HOT 2
- Healthchecks/livenessProbe does not pass when using HTTPS scheme HOT 3
- The "Debugging HTTP applications with per-route metrics" task in the documentation is broken and needs updating
- Not all gRPC errors should be retried HOT 3
- Traffic split not working with ExternalName services / services in different namespaces HOT 2
- Linkerd CNI repair controller does not listen on IPv6 HOT 1
- Setting `-log-level debug` introduces `client-go` logging at the `INFO` level HOT 1
- Improve `linkerd viz check` to have skip prom clusterrole checks when prom controller is disabled HOT 3
- Increase startup and liveness probe timeout for linkerd-destination HOT 4
- linkerd/client image cannot be found on cr.l5d.io (ghcr.io) HOT 1
- linkerd-proxy does not evict idle metrics eventually leading to OOMKILL HOT 5
- Linkerd-proxy routing traffic to wrong pod HOT 6
- Allow setting LINKERD2_PROXY_SHUTDOWN_ENDPOINT_ENABLED in helm chart HOT 5
- linkerd-proxy: allow to add custom headers to outgoing requests
- Outbound HTTP endpoints seems to miscount "ready" endpoints with circuit breaking HOT 3
- Linkerd closing connections of long-running gRPC requests HOT 2
- edge-24.8.2 CVE-2024-41110 CRITICAL github.com/docker/docker HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from linkerd2.