Environment:
Minikube on Mac OS X

What happened:

I am trying to load NGINX-Ingress with a custom tls certificate, in this case a trusted TLS certificate I generated on my machine. I start minikube, then enable the ingress-nginx addon which deploys nginx to the kube-system namespace successfully. I create my certificate in the kube-system namespace with the title mkcert.

I then modified

Every kubeflow image should be scanned for security vulnerabilities.
It would be great to have a periodic security report.
Each of these images with vulnerability should be patched and updated.

It was far from obvious for me that the argParser for --also-proxy was of type append. The documentation could say something about the following possibility. Had to fork the code to figure this out.

  telepresence --run-shell --method vpn-tcp \
    --also-proxy example1.com \
    --also-proxy example2.com \
    --also-proxy example3.com

Is your feature request related to a problem?
"DevSpace should use the current docker behavior for dockerignore:
Dockerfile + .dockerignore
Dockerfile + Dockerfile.dockerignore
Dockerfile.frontend + Dockerfile.frontend.dockerignore
"

Which solution do you suggest?
Delegating the dockerignore file search to Docker if possible, otherwise copying the behavior as best as possible

Hi, since Helm 2.5.0, it's possible to use relative urls in index.yaml chart repository: https://github.com/helm/helm/blob/master/docs/chart_repository_faq.md

Minibroker is not compatible with that mode.

In pkg/helm/helm.go, the LoadChart function should first check if chartURL is a fully qualified URL, if not, build an URL with the relative URL and "repoURL".