[Bug] Non modyficable zap options with development: true hardcoded

[grzesuav]

Current Behavior

https://github.com/cryostatio/cryostat-operator/blob/main/internal/main.go#L88

there is

	opts := zap.Options{
		Development: true,
	}

which is not suitable for production use.

Expected Behavior

I would like to have configuration option for:

• log level - via --log-level flag
• log format - --log-format=json example flag

Steps To Reproduce

No response

Environment

- OS: 
- Environment: 
- Version:

Anything else?

If this is configurable otherwise would appreciate some pointers

[andrewazores]

https://sdk.operatorframework.io/docs/building-operators/golang/references/logging/

cryostat-operator/internal/main.go

Line 90 in 85d6445

opts.BindFlags(flag.CommandLine)

I haven't looked at this in a very long time, or tested this out recently, but I think it's intended that you can already pass through flags for zap to use. I don't know how that works with Development: true being hardcoded though.

https://github.com/kubernetes-sigs/controller-runtime/blob/717b32aede14c921d239cf1b974a11e718949865/pkg/log/zap/zap.go#L257

If you pass --zap-devel=false, maybe that will override the Development: true hardcoded value that is set before?

cryostat-operator/config/manager/manager.yaml

Line 29 in 85d6445

- --leader-elect