Currently we run this tool as Daemonset, it is being discussed few times that what will it take to make it run as a job https://kubernetes.io/docs/concepts/workloads/controllers/job/ : also, a great idea share by @arnaud-tincelin - we can scope this so that we can get pros and cons of this approach. At present I am not sure what all functionality we will not be able to deliver when run as a job because there are few logs which will run as direct commands in host etc.

A gentle ping to @JunSun17 : if you can please guide us with the daemonset option and was the job option was not done due to any specific reasons.

This is one of a good workitem to stock take and scope. Opened it as a place holder for discussion and ideas. Thanks heaps.