Hello,

According to this thread, it is possible to use some path like file://local/path/to/chart instead of some chart repository URL.

In the documentation, I do not see any examples or mention for this feature.

Can we add it to the documentation or make it more accessibl

Checklist:

• I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
• I've included steps to reproduce the bug.
• I've pasted the output of argocd version.

Describe the bug

If an invalid token for a local user exists in argocd-secret, the API will refuse to process any request with an error message similar to:

FATA[0002] rpc error: code =

I reinstalled a k3s cluster built with --no-extras and added `--k3s-extra-args="--flannel-backend=host-gw". The cluster failed to start.

I logged in and saw that the output of ps showed the following:

14760 ?        Ssl    0:40 /usr/local/bin/k3s server --cluster-init --tls-san 10.68.0.63 --flannel-backend=host-gw--n

It would be nice to have a flag that allows to keep only the last x versions of a chart.

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

First reported on Slack (https://kubernetes.slack.com/archives/C9D3TSUG4/p1550784319000900), it looks like if https://github.com/helm/monocular/blob/v1.2.0/cmd/chart-repo/utils.go#L100 comes back with an empty list (if there are no entries in the index.yaml, or all charts are deprecated), then https://github.com/helm/monocular/blob/v1.2.0/cmd/chart-repo/utils.go#L260 results in a panic as it tries

Describe the bug
If my okteto.yml has a context that doesn't exist on the active KUBECONFIG, okteto outputs the following:

invalid configuration: [context was not found for specified context: okteto-dev, cluster has no server defined]

It would be useful to have a clearer message like: '$CONTEXT' context not found in $KUBECONFIG

**Desktop (please complete the following infor

In Kubernetes 1.18 the Ingress definitions have changed slightly.

In particular the @paurosello mentioned the change about ingressClass becoming part of the spec, instead of being an annotation.

If we can add both, perhaps that will help keep backwards compatibility for the time being?

https://kubernetes.io/docs/set

Implement a gPRC version of the API (on a different port) for podinfo and generate the client in podcli.