when killing the process running helm dep up it sometimes leave a temporary folder named tmpcharts and this makes the next helm dep up fail with the following error.

Error: Unable to move current charts to tmp dir: rename /mychart/charts /mychart/tmpcharts: file exists

This is easily reproducable by creating a folder named tmpcharts inside an helm chart root folder and try to l

Checklist:

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

Describe the bug

Values from an Application CRD values block that overrides values from value files are not visualized under the App Details -> Parameters -> Parameters section.

**To Repro

This feature enables the ipsec backend for Flannel in the k3sup install command

Expected Behaviour

An additional flag to k3sup install should enable ipsec for Flannel as

Location

• Browser
• CLI
• API
• Documentation

Motivation

Connecting to AWS RDS is complicated without a step-by-step guide unique to Porter.

Requirements

• Document how to set up the RDS instance if it doesn't exist.
• Document how to connect to the RDS instance from the same VPC.
• Document how to configure VPC peering if an RDS instance already exist

The background is in #1786 .

We should allow revision created by outside system. So we should add a mechanism to check if the revision already exist.

The quick solution could be:

1. calculate the revision hash
2. list all revision related(label selector app name)
3. check if there's existing revision with same hash and compare the spec. If they are deep equal, don't generate.

_Origin

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

The buildkit (client) and buildkitd (builder daemon) can both be used with faasd or k3s hosts for building images without installing Docker onto the machine.

There is a tar that can be downloaded like we do with inletsctl, however, we need to make sure we extract both binaries. I'm fairly sure that this will "just work"

See more:

https://github.com/moby/buildkit/releases

We could add a field called status-selector to Flux get commands so that users can specify the status condition name and the desired state to filter the result.

The filter format could be flux get <kind> --status-selector=<condition-name>=<true|false|unknown> .

Print sources that are not ready:

flux get source all --status-selector=ready=false

Print Kustomizations with f

Describe the bug
At this moment, we silently ignore these values, which creates confusion.

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