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

[kube] add server_id to targets when monitoring exec/portforward connections #47829

Merged
merged 1 commit into from
Oct 29, 2024

Conversation

tigrato
Copy link
Contributor

@tigrato tigrato commented Oct 22, 2024

This PR adds the target server_id (kubernetes service) when proxy establishes a connection to support kubectl exec and portforward. This allows proxies to terminate early the connection without relying on the upstream to terminate it.

…ections

This PR adds the target server_id (kubernetes service) when proxy establishes a connection to support kubectl exec and portforward. This allows proxies to terminate early the connection without relying on the upstream to terminate it.
Copy link

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-47829.d3pp5qlev8mo18.amplifyapp.com

@tigrato tigrato requested a review from rosstimothy October 29, 2024 10:19
@public-teleport-github-review-bot public-teleport-github-review-bot bot removed the request for review from fspmarshall October 29, 2024 14:41
@tigrato tigrato enabled auto-merge October 29, 2024 15:11
@tigrato tigrato added this pull request to the merge queue Oct 29, 2024
Merged via the queue into master with commit 9d4b20c Oct 29, 2024
43 checks passed
@tigrato tigrato deleted the tigrato/kube-exec branch October 29, 2024 15:31
@public-teleport-github-review-bot

@tigrato See the table below for backport results.

Branch Result
branch/v14 Create PR
branch/v15 Create PR
branch/v16 Create PR
branch/v17 Create PR

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