Output of helm version:

Client: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}

Output of kubectl version:

Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.7", GitCommit:"d

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

• Documentation
• Browser
• CLI
• API

Motivation

It should be possible to connect to each database through porter run. Some databases may require a separate worker service that runs a client for that database.

Requirements

Document how to connect to each of the 3 databases through porter run:

• [Postgres](https://docs.getporter.dev/docs/p

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

With raw kube approach, we can easily have a built-in ComponentDefinition to reference a Git repo as a component (using Flux Kustomization as example but there're many approaches indeed):

apiVersion: core.oam.dev/v1beta1
kind: ComponentDefinition
metadata:
  name: foo
  namespace: default
spec:
  workload: 
    definition: 
      apiVersion: apps/v1
      kind: Deployment # 

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

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

The TOC on the right hand side of https://toolkit.fluxcd.io/guides/helm-operator-migration/ is very crowded, let's add a mini-TOC at the top of the document to provide links to:

• discussion of breaking changes
• api spec changes
• migration strategy
• FAQ

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