Skip to content

Conversation

@vietj
Copy link
Member

@vietj vietj commented Oct 8, 2025

Motivation:

Support dynamic token resolution for Kubernetes resolver, since tokens can be ephemeral.

Changes:

Update the resolver creation with a token provider called initially and upon 401 errors.

Motivation:

Support dynamic token resolution for Kubernetes resolver, since tokens can be ephemeral.

Changes:

Update the resolver creation with a token provider called initially and upon 401 errors.
@vietj vietj added this to the 5.1.0 milestone Oct 8, 2025
@vietj vietj self-assigned this Oct 8, 2025
@vietj
Copy link
Member Author

vietj commented Oct 8, 2025

@MichalKoziorowski-TomTom can you have a look ?

@vietj vietj merged commit fb33f50 into main Oct 9, 2025
4 checks passed
@vietj vietj deleted the token-provider branch October 9, 2025 06:30
@vietj vietj mentioned this pull request Oct 9, 2025
@MichalKoziorowski-TomTom
Copy link
Contributor

@vietj Sorry for delay. I've just seen your message.
Idea with token provider looks really good and solves the issue.
Thank you for fixing another issue with ServiceAddress and port. This will really reduce number of needed hacks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants