Alexandre Proulx

I don't know, I feel like this is something else. pylint is not managed the same way in v6.9.x python image, or dependency link is broken.. ➜ ~ docker run...

No request or usage data found during RAM allocation calculation. Setting allocation to 0.

This might be valid for some prometheus setup, but in our case it shows double CPU on pod view. https://github.com/lensapp/lens/blob/f1a960fd785b62a118acd8b1525d879f39917e21/packages/technical-features/prometheus/src/operator-provider.injectable.ts.ts#L83 

Meanwhile, is there any workaround for something like this? ```json { "features": { "ghcr.io/devcontainers-contrib/features/asdf-package:1": { "plugin": "aws-vault" } "ghcr.io/devcontainers-contrib/features/asdf-package:1": { "plugin": "consul" } } } ```

Same here, I used the `kustomize edit fix` and now the namespace replacement is not working anymore. Running on linux and inside devcontainer in vscode.

Was able to make `v2.5.5` work by adding the `application.namespaces` to the `argocd-cmd-params-cm`. I had no other choices then to kill the pods to make them reload the config. Might...

Using kustomize would look somehow like this: ``` --- apiVersion: kustomize.config.k8s.io/v1beta1 kind: Kustomization bases: - github.com/argoproj/argo-cd//manifests/ha/cluster-install?ref=v2.5.5 configMapGenerator: - behavior: merge literals: - server.insecure="true" - application.namespaces="*" name: argocd-cmd-params-cm ``` ``` apiVersion:...

@ironoa did you remove your pods after changing the configmap? If not, try this ``` kubectl scale statefulset/argocd-application-controller --replicas=0 -n argocd kubectl scale deployment/argocd-server --replicas=0 -n argocd kubectl scale statefulset/argocd-application-controller...

Can you run `kubectl get configmap argocd-cmd-params-cm -n argocd -o yaml` and validate it contains ``` data: application.namespaces: '*' ```

Maybe upgrading helm chart 5.16.9, which uses v2.5.5 might help?