Linkerd Joins the Cloud Native Computing Foundation
blog.buoyant.io
Linkerd Joins the Cloud Native Computing Foundation
1–10 of 13 posts
Re: Linkerd Joins the Cloud Native Computing Foundation
#2Re: Linkerd Joins the Cloud Native Computing Foundation
#3Not sure about this one yet - some benefits, but not really massive traction. I don’t clearly see the benefits (although latency-sensitive internal loadbalancing seems quite neat), but it’s yet-another proxy in the neverending proxying of proxies within K8S already.
Re: Linkerd Joins the Cloud Native Computing Foundation
#4Not sure about this one yet - some benefits, but not really massive traction. I don’t clearly see the benefits (although latency-sensitive internal loadbalancing seems quite neat), but it’s yet-another proxy in the neverending proxying of proxies within K8S already.
Re: Linkerd Joins the Cloud Native Computing Foundation
#5Not sure about this one yet - some benefits, but not really massive traction. I don’t clearly see the benefits (although latency-sensitive internal loadbalancing seems quite neat), but it’s yet-another proxy in the neverending proxying of proxies within K8S already.
" it’s yet-another proxy in the neverending proxying of proxies within K8S already." - <3
Re: Linkerd Joins the Cloud Native Computing Foundation
#6I have requested for L4 support in Linkerd that will finally make it possible for Linkerd to actually become an ingress + Service abstraction.
Re: Linkerd Joins the Cloud Native Computing Foundation
#7Re: Linkerd Joins the Cloud Native Computing Foundation
#8Re: Linkerd Joins the Cloud Native Computing Foundation
#9The killer application of linkerd is kubernetes, where a lot of people are using linkerd to get around using Kubernetes "Services". I think the Ingress controllers talk directly to Linkerd. I have requested for L4 support in Linkerd that will finally make it possible for Linkerd to actually become an ingress + Service abstraction.