Andrei Kvapil

To me it would be very convenient way to pass parameters via data url. Eg. something like this: ```jsonnet local p = import '../../params.libsonnet'; local params = p.components.victoriametrics; local chart...

My bad **Release Names** were removed from Helm3 https://helm.sh/docs/faq/#release-names-are-now-scoped-to-the-namespace Not a bug, removing `name` parameter from `std.native('expandHelmTemplate')` makes helm templating working again

Reopen, there is still need an opportunity to specify name for the releases, eg: ```bash # For Helm 2 helm install --namespace --name gitlab-runner -f gitlab/gitlab-runner # For Helm 3...

Good workaround is to use `--name-template` flag, it's working fine with both: Helm2 and Helm3 example component: ```jsonnet local env = { name: std.extVar('qbec.io/env'), namespace: std.extVar('qbec.io/defaultNs') }; local p =...

@harsimranmaan how about using `--name-template`? It is supported by both helm2 and helm3

Yes, I'm going to use qbec with Argo CD, example setup: https://github.com/argoproj/argo-cd/issues/2930#issuecomment-686048925

I don't know, may be because I was testing it on newest 1.19

By the way, I've decided that symlinks can solve partially this problem: Eg user can do: ``` git submodule add https://github.com/kvaps/some-qbec-application pkg/some-qbec-application (cd components/; ln -s ../pkg/some-qbec-application/components/* .) ``` To...

This is a good question, Argo CD is fully rely on state described in Git. Even small difference in resources definition in Git and Kubernetes applied manifests causes OutOfSync error,...

> I think as long as there are 2 annotations potentially in conflict, picking any one will always cause some case to fail. That's not fully true, as the only...