version: Bump nydus snapshotter to v0.13.13

[ChengyuZhu6]

Bump nydus snapshotter to v0.13.13 to fix the gap when switching different snapshotters in guest pull.

Fixes: #8407

[stevenhorsman]

LGTM. Thanks!

[fidencio]

/test

[fidencio]

lgtm, thanks @ChengyuZhu6!

[wainersm]

Hi all!

Not related exactly with this PR but saying here because I got your audience ;)

Looking at the non-tee job to see if this change deployed the v0.13.13 I realized that it's actually fetching the latest image (ghcr.io/containerd/nydus-snapshotter:latest):

 Normal  Scheduled  5s    default-scheduler  Successfully assigned nydus-system/nydus-snapshotter-j2vmp to aks-nodepool1-98563127-vmss000000
    Normal  Pulling    5s    kubelet            Pulling image "ghcr.io/containerd/nydus-snapshotter:latest"
    Normal  Pulled     1s    kubelet            Successfully pulled image "ghcr.io/containerd/nydus-snapshotter:latest" in 3.55s (3.55s including waiting)
    Normal  Created    1s    kubelet            Created container nydus-snapshotter
    Normal  Started    1s    kubelet            Started container nydus-snapshotter

Looking at https://github.com/containerd/nydus-snapshotter/blob/v0.13.13/misc/snapshotter/base/nydus-snapshotter.yaml#L42 .... yeah... using latest.

You know I'm a big fan of pinning versions, so I think we should pin this properly as well. I see two options here:

1. On our CI, change the image tag before apply. Somewhere here: https://github.com/kata-containers/kata-containers/blob/main/tests/integration/kubernetes/gha-run.sh#L472
2. Ask nydus-snapshotter community to pin the version themselves at release time (IMHO they should). In our side we implement some safe-guard, e.g., check the deployed image is the version expected

[stevenhorsman]

Looking at the non-tee job to see if this change deployed the v0.13.13 I realized that it's actually fetching the latest image (ghcr.io/containerd/nydus-snapshotter:latest):

Yeah - @mkulke and I were chatting about this on slack earlier and thought that we'd either user kustomize to update the image, or ideal request the nydus-snapshotter community to pin the version, which we felt was the better solution (and then we follow that by pinning our operator image too!). So to repeat your words - we are also in agreement that the best way is to ask nydus-snapshotter for the update as part of their release process I guess?

[fidencio]

@stevenhorsman, @wainersm, I fully agree, and I'm assuming we will be able to work on the items as follow-ups.
For noiw, merging this one.

[ChengyuZhu6]

Yeah - @mkulke and I were chatting about this on slack earlier and thought that we'd either user kustomize to update the image, or ideal request the nydus-snapshotter community to pin the version, which we felt was the better solution (and then we follow that by pinning our operator image too!). So to repeat your words - we are also in agreement that the best way is to ask nydus-snapshotter for the update as part of their release process I guess?

I have created a pr to fix it. containerd/nydus-snapshotter#596