artem-nefedov

Hi @SomtochiAma Unfortunately, this is reproduced on a private repo. Also, when I intentionally try to reproduce it (with either private or public repo), I don't have any success. It...

> Looking at https://github.com/fluxcd/flux2/blob/main/cmd/flux/create_source_helm.go#L199, it seems there was really no artifact in helm repository. Maybe the helm chart isn't ready yet and some seconds later (when you run the second...

@gusfcarvalho sure ```yaml --- apiVersion: external-secrets.io/v1alpha1 kind: ClusterSecretStore metadata: name: aws-secrets-manager spec: provider: aws: region: us-west-2 service: SecretsManager --- apiVersion: external-secrets.io/v1alpha1 kind: ExternalSecret metadata: name: example spec: data: - remoteRef:...

@stefanprodan Sure. Here's the info you asked, as well as full log of actions from scratch: ``` ➜ k get ns foo Error from server (NotFound): namespaces "foo" not found...

@stefanprodan Thanks! Changing to `v1beta2` actually solved the problem. The weird thing is that, if my Kustomization manifest in helm chart says `v1beta1`, the manifest in cluster shows `v1beta2`, which...

@stefanprodan As I mentioned in my first post, the issue can be also reproduced with no helm at all, using only kubectl: If I delete kustomization like this, namespace WILL...

@SomtochiAma Sorry, maybe I was not clear. I used the local kustomize just to show how patch will work. To reproduce the issue with flux, you need: 1. Contents of...

Any progress on this issue? Based on last status, I believe it was successfully reproduced?

Just tested it: explicit `null` still gets replaced with `{}`, and the issue still occurs. `nil` is a type error because it's just a string.

Have you considered changing this requirement? It leads to unnecessary duplication - same thing has to be specified in target and in patch. Sometimes it is useful, but more often...