Skip to content

fix: get workload cluster client from proper kubeconfig#1349

Draft
apedriza wants to merge 1 commit intok0sproject:mainfrom
apedriza:use-tunneling-secret-for-workload-client
Draft

fix: get workload cluster client from proper kubeconfig#1349
apedriza wants to merge 1 commit intok0sproject:mainfrom
apedriza:use-tunneling-secret-for-workload-client

Conversation

@apedriza
Copy link
Contributor

@apedriza apedriza commented Feb 9, 2026

fix #726

@apedriza apedriza force-pushed the use-tunneling-secret-for-workload-client branch from 3e1cfae to 5d56645 Compare February 10, 2026 11:43
Signed-off-by: apedriza <adripedriza@gmail.com>
@apedriza apedriza force-pushed the use-tunneling-secret-for-workload-client branch from 5d56645 to 63b0964 Compare February 10, 2026 11:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Use connection tunneling internally

1 participant