Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Non-interactive k8s sessions in Session Recordings page do not show username #49254

Open
stevenGravy opened this issue Nov 20, 2024 · 0 comments · May be fixed by #49257
Open

Non-interactive k8s sessions in Session Recordings page do not show username #49254

stevenGravy opened this issue Nov 20, 2024 · 0 comments · May be fixed by #49257
Labels
audit-log Issues related to Teleports Audit Log bug kubernetes

Comments

@stevenGravy
Copy link
Contributor

stevenGravy commented Nov 20, 2024

Expected behavior:

The user involved in a k8s non-interactive session session would show.

Current behavior:

A non-interactive session for k8s does not include the username in the listed Session Recordings.

Image

Bug details:

  • Teleport version: 17.0.1
  • Recreation steps
  1. Connect to a k8s cluster with tsh
  2. Run a command that does a non-interactive command

kubectl exec po/mypod hostname

  1. Review the session recordings
@stevenGravy stevenGravy added audit-log Issues related to Teleports Audit Log bug kubernetes labels Nov 20, 2024
@stevenGravy stevenGravy changed the title Non-interactive k8s sessions in Session Recordings page do not show username Non-interactive k8s sessions show twice in Session Recordings page and do not show username Nov 20, 2024
@stevenGravy stevenGravy changed the title Non-interactive k8s sessions show twice in Session Recordings page and do not show username Non-interactive k8s sessions in Session Recordings page do not show username Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
audit-log Issues related to Teleports Audit Log bug kubernetes
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant