[kube] fixes duplicated session recordings in root and leaf clusters#47910
[kube] fixes duplicated session recordings in root and leaf clusters#47910
Conversation
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
|
I know this wasn't intentional but this can be considered as a feature by some users. I would consider this change breaking and not backport it to older versions. |
IMO this is a bug and we should fix it to be consistent with the recording behavior observed for other protocols. @russjones what do you think? |
81fa5b0 to
06d86e1
Compare
This PR addresses a bug in Kubernetes session recordings where both the root proxy and the leaf cluster's Kubernetes services were recording the same session, resulting in the session being available in both clusters. This behavior was inconsistent with other protocols, where recordings of leaf resources are only accessible in leaf clusters. To maintain consistency, this PR removes session recordings on the root clusters. Signed-off-by: Tiago Silva <tiago.silva@goteleport.com>
06d86e1 to
6b69d47
Compare
This PR addresses a bug in Kubernetes session recordings where both the root proxy and the leaf cluster's Kubernetes services were recording the same session, resulting in the session being available in both clusters.
This behavior was inconsistent with other protocols, where recordings of leaf resources are only accessible in leaf clusters. To maintain consistency, this PR removes session recordings on the root clusters.
Changelog: Fixes bug in Kubernetes session recordings where both root and leaf cluster recorded the same Kubernetes session. Recordings of leaf resources are only available in leaf clusters.