Can't apply new VolumeConfig with encryption

[SoulKyu]

Hello !

When i try to add encryption to my VolumeConfig, i have this error : unknown keys found during decoding

 talosctl patch machineconfig -n 10.6.46.11 --patch-file patches/storages.yaml

unknown keys found during decoding:
encryption:
    provider: luks2
    keys:
        - slot: 0
          kms:
            endpoint: https://talos-kms-vault.company.in:443
            # ---
            # apiVersion: v1alpha1
            # kind: VolumeConfig
            # name: IMAGE-CACHE
            # provisioning:
            #   diskSelector:
            #     match: system_disk
            #   grow: true
            # encryption:
            #   provider: luks2
            #   keys:
            #     - kms:
            #         endpoint: https://talos-kms-vault.company.in:443
            # ---
            # apiVersion: v1alpha1
            # kind: VolumeConfig
            # name: STATE
            # provisioning:
            #   diskSelector:
            #     match: system_disk
            #   grow: true
            # encryption:
            #   provider: luks2
            #   keys:
            #     - kms:
            #         endpoint: https://talos-kms-vault.company.in:443

Talos version is 1.11.1

Here is the patche file :

apiVersion: v1alpha1
kind: VolumeConfig
name: EPHEMERAL
provisioning:
    diskSelector:
        match: system_disk
    grow: true
    minSize: 70GB
encryption:
    provider: luks2
    keys:
        - slot: 0
          kms:
            endpoint: https://talos-kms-vault.company.in:443

Here is what i get from current config :

    apiVersion: v1alpha1
    kind: VolumeConfig
    name: EPHEMERAL
    provisioning:
        diskSelector:
            match: system_disk
        grow: true
        minSize: 70GB

Did you know what i do wrong ?

Actually the deprecated method using machine systemDiskEncryption look to work, but I would prefer not to migrate later.

[smira]

If your talosctl also 1.11.1 ?

[SoulKyu]

Ahah ! You are right, i'm 1.10.4 on the client.

I try update tomorow, but its certainly the issue!

Thanks you