![]() ![]() Manage the watch dog as a subprocess to the efs-plugin. This approach could work but is a bit messy and reduces process isolation from namespace. Also because watch dog is working against a shared efs state file(s) under /var/run/efs, this requires sharing of the file across efs-plugin and watch dog container. However, this requires sharing PID namespace so that the watch dog can kill the stunnel processes what are in the efs-plugin namespace that are different to the watch dog process namespace. This approach leverages kubelet being the init system, so that the container will be restarted once crashes. There are two ways I can think of to solve the problem:Ĭreate a new container, efs-watch-dog, in the efs node daemonset pod. And running systemd in a docker container is not trivial. The watch dog is designed for a non-containerized environment where systemd or initd is required to monitor and restart the process if it crashes. I did some quick test by starting the amazon-efs-mount-watchdog from efs mount helper, there are several challenges when using the exiting watch dog. ![]() 20:49:30,700 - WARNING - Could not start amazon-efs-mount-watchdog, unrecognized init system "aws-efs-csi-dri " ![]() Bash-4.2# cat /var/log/amazon/efs/mount.log ![]()
0 Comments
Leave a Reply. |