Skip to content

[v16] Teleterm: fix incorrect cluster URI when fetching kube namespaces on a leaf cluster#48990

Merged
kimlisa merged 2 commits intobranch/v16from
lisa/v16/teleterm-fix
Nov 14, 2024
Merged

[v16] Teleterm: fix incorrect cluster URI when fetching kube namespaces on a leaf cluster#48990
kimlisa merged 2 commits intobranch/v16from
lisa/v16/teleterm-fix

Conversation

@kimlisa
Copy link
Copy Markdown
Contributor

@kimlisa kimlisa commented Nov 14, 2024

backport #48786 to branch/v16

conflict with pb file, fixed with make grpc

changelog: Fix incorrect cluster name when querying for Kubernetes namespaces on a leaf cluster for Connect UI.

…a leaf cluster (access request) (#48786)

* Use tc.SiteName over cluster.Name

* Teleterm: fix fetching namespaces with incorrect cluster URI

If you add a root and leaf kube cluster,and on leaf Teleport cluster,
listing namespaces for root kube cluster was referring to incorrect
Teleport cluster URI

* Teleterm: fix re-ordering of selected namespaces when done selecting

Web UI still has this weird re-ordering because web UI still stores
resource ids in a map which doesn't preserve order

* Add requested length test

* Address CR

* Address CRs
@aws-amplify-us-west-2
Copy link
Copy Markdown

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

Access this pull request here: https://pr-48990.d212ksyjt6y4yg.amplifyapp.com

@kimlisa kimlisa added this pull request to the merge queue Nov 14, 2024
Merged via the queue into branch/v16 with commit 25b442f Nov 14, 2024
@kimlisa kimlisa deleted the lisa/v16/teleterm-fix branch November 14, 2024 22:31
@fheinecke fheinecke mentioned this pull request Apr 9, 2025
@fheinecke fheinecke mentioned this pull request Jan 8, 2026
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