Oleksandr Vorona

I'm observing the same behaviour with multiple hosts specified. Single host works fine though.

We use helm-secrets for some time with ApplicationSet ```yaml --- apiVersion: argoproj.io/v1alpha1 kind: ApplicationSet metadata: name: test-dev-0 namespace: argocd spec: goTemplate: true goTemplateOptions: [ "missingkey=error" ] generators: - git: repoURL:...

> I guess it works for you? @voron Yes, it works for us in multiple environments and multiple clients > Does it works out of the box? I did not...

>Is your$values/{{ .values.env }}/secrets/{{ .values.app }}.yaml file just an encrypted yaml file or it has some specific structure? It's sops-encrypted yaml file, f.e: ```yaml secrets: env: stringData: REDIS_PORT: ENC[AES256_GCM,data:nagq1Q==,iv:h7JJFPM5WvjmdDkmfdrO8QM7FG55L3UnQlKCthE/omY=,tag:h+Lh3ET5Dd51ZSZwNukGew==,type:int] REDIS_CACHE_DB:...

There is [no such option](https://cloud.google.com/kubernetes-engine/docs/reference/rest/v1/NodeConfig) in GKE node pool API support to configure disk IOPS/throughput for the node's main/boot disk. Thus I don't expect this feature to appear anytime soon....

> seems that its supported via https://github.com/GoogleCloudPlatform/magic-modules/pull/14600/files I don't see the support in terraform GKE modules yet, but it's good to know things [are done](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/container_cluster#nested_boot_disk) on GCP provider side.

It's unlikely it's possible to implement something similar at the moment due to [network restrictions on runners](https://github.com/actions/runner/discussions/3251)