Move logger initialization before k8s client creation #264
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ctrl.Log var contains noop logger until logger instance is
explicitly set with ctrl.SetLogger function
If error happen during k8s client creation it will be not logged
because ctrl.SetLogger is called after.
Move logger initialization step before k8s client
creation to be able to log client initialization errors.
Log messages when kubecofig unavailable
Before patch:
After patch: