helm: allow configuration of zap flags via helm values

[hown3d]

Motivation

Currently there is no way to configure the logging config of the yawol controllers.
This PR adds support to pass this configuration via helm values.

New helm values

Key	Type	Default	Description
logging	object	{"encoding":"console","level":"info","stacktraceLevel":"error"}	values are passed as zap-flags to the containers. See https://pkg.go.dev/sigs.k8s.io/controller-runtime@v0.18.4/pkg/log/zap#Options.BindFlags for more information
logging.encoding	string	"console"	log encoding (one of 'json' or 'console')
logging.level	string	"info"	Level to configure the verbosity of logging. Can be one of 'debug', 'info', 'error' or any integer value > 0 which corresponds to custom debug levels of increasing verbosity
logging.stacktraceLevel	string	"error"	level at and above which stacktraces are captured (one of 'info', 'error' or 'panic')

[Kumm-Kai]

Looks good! One small nit :)

[nschad]

I would have added a generic block extraArgs where the user can specify what he needs. This seems unflexible and needs adoption everytime a flag changes or a new one is added

Example: https://github.com/cortexproject/cortex-helm-chart/blob/master/templates/alertmanager/alertmanager-dep.yaml#L106-L108

[hown3d]

I would have added a generic block extraArgs where the user can specify what he needs. This seems unflexible and needs adoption everytime a flag changes or a new one is added

Example: cortexproject/cortex-helm-chart@master/templates/alertmanager/alertmanager-dep.yaml#L106-L108

I agree in general to add extraArgs as a value but having only extraArgs removes the abstraction of the values completely. I don't want to check if the application beneath uses zap as logging framework or however I can configure logging, I just want to configure it easily as a user.