Added new Log Enconder Config

[yuriolisa]

Description:

Added 5 new parameters to enable a customized JSON log Encoder:
--enable-customized-log-encoder = It will enable the feature to set customized keys and formats to the logs, otherwise, the operator will use the zap-devel config.
--log-message-key = It will replace the Key of the Message field (e.g. "msg")
--log-level-key = It will replace the Key of the Level field (e.g. "severity")
--log-time-key= It will replace the Key of the Time field (e.g. "timestamp")
--log-time-format = It will replace the Format of the Time field (e.g. "epoch", "epochmillis", "epochnano", "iso8601", "rfc3339" or "rfc3339nano")
--log-level-format = It will replace the Format of the Level field (e.g. "uppercase", "lowercase")

Link to tracking Issue(s):

• Resolves: Configure zap EncoderConfig for operator #268

Testing:

Documentation:

[swiatekm]

Some of these can be set via existing flags: https://pkg.go.dev/sigs.k8s.io/controller-runtime/pkg/log/zap#Options.BindFlags. If we need to add more, can we use the existing naming convention?

[yuriolisa]

Some of these can be set via existing flags: https://pkg.go.dev/sigs.k8s.io/controller-runtime/pkg/log/zap#Options.BindFlags. If we need to add more, can we use the existing naming convention?

I'm aware of these BindFlags options, but when you set a new Enconderconfig you have to populate these values as well, due to that I've put these parameters.
The name convention is a good option, however, the use case for that issue is to deliver an option to the users to customize their operator logs' fields.

[swiatekm]

Some of these can be set via existing flags: https://pkg.go.dev/sigs.k8s.io/controller-runtime/pkg/log/zap#Options.BindFlags. If we need to add more, can we use the existing naming convention?

I'm aware of these BindFlags options, but when you set a new Enconderconfig you have to populate these values as well, due to that I've put these parameters. The name convention is a good option, however, the use case for that issue is to deliver an option to the users to customize their operator logs' fields.

I think you can use Options.EncoderConfigOptions to modify the encoder config without overwriting it? Right now, we have a --zap-time-encoding which appears to do the same thing as your --log-time-format. We should either use the existing flag or remove it and use the new one.

[swiatekm]

Are the defaults here the same as we currently have? That is, if we don't set any of these, there's no change in behaviour?

[yuriolisa]

Yes, but we can't compare it with the current log because we use the console encoder by default, while these changes will be effective when we set the zap-encoder=json.

[swiatekm]

LGTM, modulo the lint failure.

[jaronoff97]

@yuriolisa can you also please update some docs too for this change? This would assist with the feedback we got in #873

[jaronoff97]

🚀 🎉