Boban Petrovic

Its posix. But how it detects cpu usage? Its posix isolator for cpu too.

This is what our mesos slaves return: ``` { "executor_id": "kg45", "executor_name": "", "framework_id": "Singularity", "source": "test_template_test_job_2-test_job_2_deploy_19-1519399684082-1-db07-DEFAULT", "statistics": { "cpus_limit": 0.2, "cpus_system_time_secs": 1324.95, "cpus_user_time_secs": 1780.07, "mem_limit_bytes": 201326592, "mem_rss_bytes": 596295680, "timestamp":...

Does `helmfile` still require `kustomize` binary?

It seems it doesn't, from #1736 . This issue should be reviewed and closed.

Here are some examples of security vulnerabilities reported by XRay, for v0.143.0, alpine image.  

It seems that those vulnerabilities are not introduced by helmfile itself, but helm plugins. I'm experimenting to find out what can be done.