We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Grafana-operator documentation mentions usage of --zap-level=n However, zap itself uses --zap-log-level=n (https://github.com/kubernetes-sigs/controller-runtime/blob/master/pkg/log/zap/zap.go#L280-L282) When we used --zap-level in our custom grafana-operator, we faced a problem. Is it a bug in documentation?
The text was updated successfully, but these errors were encountered:
fix #762
27f44aa
1a75ad9
HubertStefanski
No branches or pull requests
Grafana-operator documentation mentions usage of --zap-level=n
However, zap itself uses --zap-log-level=n (https://github.com/kubernetes-sigs/controller-runtime/blob/master/pkg/log/zap/zap.go#L280-L282)
When we used --zap-level in our custom grafana-operator, we faced a problem.
Is it a bug in documentation?
The text was updated successfully, but these errors were encountered: