This message was deleted.
# k3s
a
This message was deleted.
c
K3s is Kubernetes so…
The error would appear to come from your crio config, have you looked at the docs there?
We don’t ship with it and don’t test with it so I’m not super familiar with it
a
Appreciate for the quick response. Yes, I checked the docs in crio and I'm following this doc to test checkpoint and restore functionality in kubernetes. https://kubernetes.io/blog/2022/12/05/forensic-container-checkpointing-alpha/
c
what version are you using?
a
Copy code
$ k3s --version
k3s version v1.32.8+k3s1 (fe896f7e)
go version go1.23.11

$ crio --version
crio version 1.32.9
c
I don’t see anything in there about enabling container image signature verification, was that something you had configured previously?
a
This is what the doc says, is there anything special I need to do in k3s to enable it?
The feature is behind a feature gate, so make sure to enable the ContainerCheckpoint gate before you can use the new feature.
c
yes, you need to enable the feature gate, as it says
a
How can I do it in k3s?
c
same as you would on any distro, with the --feature-gates arg for the component you want to enable the feature-gate on
--kubelet-arg=feature-gates=MyExampleGate=true
I don’t know if you need to enable it on just the kubelet, or also apiserver, scheduler, and so on. upstream docs may tell you that
a
Okay, also I have a multi-node HA k3s cluster. If I enable it on a k3s-server, will the flags propagate to other masters and agent nodes as well?
c
no, you need to set them everywhere you want them set.
a
Got it, thanks for all the help!