Skip to content

How to predefine KUBECONFIG localion for tsh kube? #65529

@riuvshyn

Description

@riuvshyn

Applies To

tsh kube

Details

I am looking for a way to have similar user experience as it used to be with v17 where I could:

  • logged in once - session is available for all terminal sessions
  • logged in to another cluster it appends kubeconfig so then I can use kubectl --context
  • using kubectl without running tsh proxy or tsh kubectl which is very painful

How can I configure teleport client to always use specified KUBECONFIG?

How will we know this is resolved?

Related Issues

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions