Waldek Kozba
Waldek Kozba
+1 System: OS X 10.9.5 Atom: 1.2.4
As this has been closed - does it mean the feature is perceived as unimportant and disappears from the Linkerd roadmap?
@klingerf Our use case leverages the automatic TLS certificate lifecycle management for services exposed via *k8s Ingress* using [LetsEncrypt](https://letsencrypt.org/) and the [kube-lego](https://github.com/jetstack/kube-lego) mentioned before by @esbie. Currently I'm using [NGINX...
> Looking at other projects (flux for instance), we can also consider to standardize reading a `kubeconfig` from Secret/ConfigMap to pull all configuration (endpoints, ca, auth). Flux, ArgoCD and Crossplane...
Still on this because of https://github.com/npm/cli/pull/198 and then a dependency chain: ```semantic-release > @semantic-release/npm > npm > npm-lifecycle > node-gyp > fstream```
The good in bad is that all this mess concerns the `devDependencies` only, so - there are no security issues in the runtime context.
Hi, @kinow : yes, it actually solves a real performance issue in my use case (inheritance plugin together with the Active Choices Plugin with most of the variables defined in...