[v15] Reissue kube certs when assuming access request #51057
Merged
Conversation
This file contains 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
* Reissue kube certs when assuming access request * Fix and add tests * Explain when the cert can be not found * Replace `clearCertsFn` with `middleware` field * Improve iterating over gateways * Improve a comment (cherry picked from commit e4e09a1)
ravicious
approved these changes
Jan 15, 2025
marcoandredinis
approved these changes
Jan 15, 2025
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Backport #50553 to branch/v15
changelog: Assuming an Access Request in Teleport Connect now propagates elevated permissions to already opened Kubernetes tabs