Replies: 3 comments 3 replies
-
The RGW case makes sense, however, I have mixed feelings about this. I'm always hoping not to clutter the CRD too much. Changing the log level is not something the user has to do very often, so I'm sure if it's worth a CR spec addition at this point. If RGW is tricky we could simply solve this with some additional documentation. Also, I wonder if just applying |
Beta Was this translation helpful? Give feedback.
-
I think this will be a good way of making easier and more understandable the logging levels, besides it can give more quick knowledge of the log level without having to get into the operator container. |
Beta Was this translation helpful? Give feedback.
-
Making the log levels simpler to set will be a helpful addition to the Krew plugin. |
Beta Was this translation helpful? Give feedback.
-
currently, changing the daemons log level is done via the toolbox.
in the case of the RGW this is difficult because the user needs to know the client id of the RGW.
e.g.
instead, it would be easier to set as a parameter in the cluster CR for osd, mon and mgr (could be per daemon as they already have per daemon sections in the CR). and could be in the object store CR for the rgw (under the gateway section).
please let me know what you think?
Beta Was this translation helpful? Give feedback.
All reactions