Skip to content

[v17] kube: fix transport being incorrectly cached by kube service#51652

Merged
tigrato merged 1 commit intobranch/v17from
bot/backport-51640-branch/v17
Jan 30, 2025
Merged

[v17] kube: fix transport being incorrectly cached by kube service#51652
tigrato merged 1 commit intobranch/v17from
bot/backport-51640-branch/v17

Conversation

@tigrato
Copy link
Copy Markdown
Contributor

@tigrato tigrato commented Jan 30, 2025

Backport #51640 to branch/v17

changelog: Fixes a regression that caused the Kubernetes Service to reuse expired tokens when accessing EKS, GKE and AKS clusters using dynamic credentials.

PR #46899 introduced a subtle change in Kubernetes service behavior, where the direct transport—kube agent to Kubernetes API—is now cached for five hours.

This disrupts auto-discovery because tokens are only valid for 15 minutes, while the HTTP transport that applies them remains valid for five hours. As a result, the Kubernetes service continues using the same expired token for 4 hours and 45 minutes.

This PR resolves the issue by preventing token caching altogether.

Fixes #51639

Signed-off-by: Tiago Silva <tiago.silva@goteleport.com>
@tigrato tigrato enabled auto-merge January 30, 2025 15:44
@public-teleport-github-review-bot public-teleport-github-review-bot Bot removed the request for review from smallinsky January 30, 2025 16:20
@tigrato tigrato added this pull request to the merge queue Jan 30, 2025
Merged via the queue into branch/v17 with commit c16ef82 Jan 30, 2025
@tigrato tigrato deleted the bot/backport-51640-branch/v17 branch January 30, 2025 16:40
@camscale camscale mentioned this pull request Feb 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants