Use shared clustercache from libsveltos; invalidate cache on auth errors#1878
Merged
Merged
Conversation
Replaces the addon-controller-local controllers/clustercache package with the shared lib/clustercache now in libsveltos, so event-manager, healthcheck-manager, and classifier can reuse the same cache instead of each managing their own (or none at all). Calls InvalidateOnAuthError in handleDeployerError and processUndeployResult so a cached rest.Config/mapper/discovery-client (and the underlying workload-identity cache entry) gets evicted as soon as the API server rejects credentials with 401/403, rather than only on TTL expiry or an explicit cluster delete.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Replaces the addon-controller-local controllers/clustercache package with the shared lib/clustercache now in libsveltos, so event-manager, healthcheck-manager, and classifier can reuse the same cache instead of each managing their own (or none at all).
Calls InvalidateOnAuthError in handleDeployerError and processUndeployResult so a cached rest.Config/mapper/discovery-client (and the underlying workload-identity cache entry) gets evicted as soon as the API server rejects credentials with 401/403, rather than only on TTL expiry or an explicit cluster delete.