I am testing Kruise on RKE2, version 1.24.
The pods created by kruise-daemon daemonset can't start by default, giving a permission denied error while accessing the containerd socket.
Adding
securityContext:
privileged: true
to the daemonset manifest solves the issue.
Is this expected behaviour, and if yes, would it be possible to add this parameter to the chart values and templates?
I am testing Kruise on RKE2, version 1.24. The pods created by
kruise-daemondaemonset can't start by default, giving apermission deniederror while accessing the containerd socket. Addingto the daemonset manifest solves the issue. Is this expected behaviour, and if yes, would it be possible to add this parameter to the chart values and templates?