Pass a logger to unmanaged sync controller to surface reconcile errors #104
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.
Summary
It looks like an unmanaged controller (in controller-rutime? or multicluster-runtime?) doesn't log its reconciler errors unless you pass a logger into it. Thus, tons of errors are swallowed without any indication why.
The "lore" behind this is that in api-syncagent's 0.3 release series, this was working. It was working because the code in controller-runtime 0.19 derived the logger for unmanaged controllers from the passed manager:
https://github.com/kubernetes-sigs/controller-runtime/blob/b901db121e1f53c47ec9f9683fad90a546688c3e/pkg/controller/controller.go#L160
This changed since then (as we are using upstream controller-runtime now, we've bumped dependencies, including controller-runtime), to be specific in this commit.
Thus, we need to pass in a logger now.
What Type of PR Is This?
/kind bug
Related Issue(s)
Fixes #
Release Notes