Closed emsixteeen closed 4 months ago
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: Once this PR has been reviewed and has the lgtm label, please assign alculquicondor for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
I thought you had to upgrade klog?
This is in lieu of upgrading klog
!
Being that the controller (in the cmd
package) already uses kubeapiserver.SetupSignalHandler()
to create the stopCh
, we can also use kubeapiserver.RequestShutdown()
to close that channel.
In the first conversation I mentioned that in order not to call klog.Fatalf()
, then either klog
would need to be upgraded, or another option could be explored. This is the other option.
By the time I tested whether kubeapiserver.RequestShutdown()
would work, the #619 was already merged! 😄
/close
let's leave it for now.
It might be better to wait to upgrade and convert all logs to structured logging.
@alculquicondor: Closed this PR.
/close
let's leave it for now.
It might be better to wait to upgrade and convert all logs to structured logging.
👍
Per this discussion in #619, this is an option to change
klog.Fatalf()
to favor of something less harsh.