Sarah Brown

This issue is blocking potential features like https://github.com/jetstack/kube-lego integration for LetsEncrypt

Also, Istio support should include [tls via ingress resources](https://istio.io/docs/tasks/ingress.html#configuring-secure-ingress-https) (not necessarily SNI, but at least dynamic cert reloading)

Hi @21stio, in your example yes `/foo/yo` is routed to service `s1` on port 80. The issue that's being referenced here is this: forwarded requests will still have a path...

Great @pawelprazak ! I'm happy to help. Currently the ingress annotations are read [here](https://github.com/linkerd/linkerd/blob/d7bdcc00563157b288c49bae4c6a98c01dd0c269/k8s/src/main/scala/io/buoyant/k8s/IngressCache.scala#L124). The linkerd ingress identifier matches paths based on regex, not path prefix (we took this idea...

Good feedback! I like the `use-capturing-groups` option. Since it's a backwards-compatible change, we could release it as early as v1.0.3 instead of waiting until v1.1.0. And it's not as limiting...

Cool! Convened w/ @adleong and it seems like the h2 requests's `:path` header should be changed since there's no uri

I have not personally seen this error message, but a quick google search suggests it's a duplicate of https://github.com/kubernetes/minikube/issues/757, with underlying issue https://github.com/kubernetes/kubernetes/issues/28610 Not sure there's anything for us to...

Take a look at https://discourse.linkerd.io/t/flavors-of-kubernetes/53

Now that https://github.com/medialize/sass.js/issues/72 is resolved and released as part of 0.10.0, is this issue fixable/fixed? Would love to use this plugin, but bourbon is holding me back ;)

That's my understanding, yeah. Or if that doesn't fix the issue, there's a [filesystem workaround](https://github.com/medialize/sass.js/issues/72#issuecomment-263916386) as well.