Refactor: Reconcile loggers, prepare for concurrent reconcilers #1836
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.
Was looking to implement an option for configuring
MaxConcurrentReconciles
when registering controllers.But realised that the Reconciler structs seem to be shared across reconcile requests, meaning
r.Log
could be replaced with context values from a later reconcileRequest.This is especially likely for
GrafanaContactPoints
due to theWatches
inGrafanaNotificationPolicy
.Kubebuilder suggests using the plain
log := log.FromContext(ctx)
Kubebuilder recommends to always have the ctx as the first argument and I have ensure that is the case as much as possible: kubebuilder controller-implementation