You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both the OLM and Catalog operators have -debug flags available that display much more useful information when diagnosing a problem. If necessary, add this flag to their deployments and perform the action that is showing undersired behavior.
but it is not clear how exactly this flag is supposed to be set, it would be good to include a patch command or alternatively an example of how to set the flag. IE. where in the deployment does the flag need to be set? Is it an additional arg like:
Yeah agreed that this is a gap in documentation - I did a poor job of conveying "this is what you can do in the meantime" in my previous comment. When playing around with the olm/catalog operators locally, it looks like both the -debug/--debug flag values are respected:
$ ./bin/catalog
INFO[0000] log level info
$ ./bin/catalog --debug
INFO[0000] setting logging level to DEBUG
$ ./bin/catalog -debug
INFO[0000] setting logging level to DEBUG
https://olm.operatorframework.io/docs/tasks/troubleshooting/olm-and-catalog-operators/#how-to-view-the-catalog-operator-logs states:
but it is not clear how exactly this flag is supposed to be set, it would be good to include a patch command or alternatively an example of how to set the flag. IE. where in the deployment does the flag need to be set? Is it an additional arg like:
or something else?
The text was updated successfully, but these errors were encountered: