You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current Kubernetes OIDC authenticator that's used in this case seems to be handling audiences and that's likely what we want in these cases - to enforce specific token audience for the KRP upstream. Isn't that the case?
What
We should use a OIDC authenticator to highlight, that it is audience agnostic. There is one upstream.
link
The text was updated successfully, but these errors were encountered: