Upstream Using InMemory token cache for admin clientset in propeller #5621
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.
Why are the changes needed?
This is an upstream of a fix that caused a panic in our fork. The source of the panic is the
nil
value set fortokenCache
when propeller is making the auth interceptor.Something misleading is happening here though... this panic'ing auth interceptor is not actually being used. These dial options are being returned up to the
authOpts
variable here. TheseauthOpts
are then only used when talking to data catalog. Data catalog is typically not authenticated, so this panic doesn't happen.The actual auth interceptor that is being used by propeller is here, in the main client builder code. This one is proactively set to a TokenCacheInMemory if nil which is why we don't see any panics.
This is still good to have however. So let's get this in.
What changes were proposed in this pull request?
How was this patch tested?
Setup process
Screenshots
Check all the applicable boxes
Related PRs
Docs link