Add global option to enable/disable init containers and sidecars

[FxKu]

Closes #464.
Error out on createStatefulSet, otherwise only warn whenever generateStatefulSet is called

[coveralls]

Coverage remained the same at 23.705% when pulling c73d55e on feature/initcontainer_sidecar_toggle into 2e9b653 on master.

[Jan-M]

How do init containers work on scaling out for example or in? Is changing init containers reflected correctly in the manifest? (does it make sense to react on changes of init container on a running cluster)

But I agree with the above comment, if init is specced in manifest and globally disabled cluster should probably not be created. Modifying an existing one is something else.

[redbaron]

How do init containers work on scaling out for example or in? Is changing init containers reflected correctly in the manifest? (does it make sense to react on changes of init container on a running cluster)

same as any other change to Stateful set's pod spec, it triggers graceful roll of all pods to new version of spec

[Jan-M]

Side car I get, but what is the value of having init containers added once the statefulset is already up and runing (I guess I need to read a bit more of K8S docs here). Maybe mixing a bit of "init of postgres" with "init of container environment"

[sdudoladov]

👍

[FxKu]

👍