removing klog.Fatalf in favor of a shutdown request

[emsixteeen]

Per this discussion in #619, this is an option to change klog.Fatalf() to favor of something less harsh.

[google-oss-prow]

[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.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[alculquicondor]

I thought you had to upgrade klog?

[emsixteeen]

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! 😄

[alculquicondor]

/close

let's leave it for now.

It might be better to wait to upgrade and convert all logs to structured logging.

[google-oss-prow]

@alculquicondor: Closed this PR.

In response to this:

/close

let's leave it for now.

It might be better to wait to upgrade and convert all logs to structured logging.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[emsixteeen]

/close

let's leave it for now.

It might be better to wait to upgrade and convert all logs to structured logging.

👍