This repository was archived by the owner on Jun 2, 2025. It is now read-only.
Fix log spam from spoke_token_controller #413
Merged
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.
Fix the log spam of the spoke_token_controller by only logging events that pass the predicate functions.
Removes the following log spam when secrets get updated somewhere in the cluster:
--- SNIP ---
I1030 02:26:00.606725 1 spoke_token_controller.go:432] secret namespace not matched, appAddonNS= open-cluster-management-agent-addon
I1030 02:26:00.864936 1 spoke_token_controller.go:432] secret namespace not matched, appAddonNS= open-cluster-management-agent-addon
I1030 02:26:01.063803 1 spoke_token_controller.go:432] secret namespace not matched, appAddonNS= open-cluster-management-agent-addon
I1030 02:26:01.325161 1 spoke_token_controller.go:432] secret namespace not matched, appAddonNS= open-cluster-management-agent-addon
--- SNAP ---