minikube

I made a mistake and put in the wrong k8s version, we should have a more beautiful looking error, and ideally do not even try to create container when a non-existing k8s version is specified

mk start --kubernetes-version=20.10.7
😄  minikube v1.21.0-beta.0 on Darwin 11.4
✨  Automatically selected the docker driver. Other choices: hyperkit, parallels, virtualbox, ssh
👍  Starting control pla

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.

Right now we emit a message like

T: Error: Unable to find cluster information
T: No current-context set. Please use the --context option to 
T: explicitly set the context.

This is all fine, but some higher-level explanation would be helpful as well, probably linking to documentation:

T: Telepresence uses kubectl/oc to access your Kubernetes/OpenShift
T: cluster. Ple

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".