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.

Sign up for GitHub

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

Jump to bottom

Modifying cluster name from the Kubernetes context #12833

Closed
Erick-Reyes opened this issue May 23, 2022 · 0 comments · Fixed by #24972
Closed

Modifying cluster name from the Kubernetes context #12833

Erick-Reyes opened this issue May 23, 2022 · 0 comments · Fixed by #24972
Labels
c-pn Internal Customer Reference feature-request Used for new features in Teleport, improvements to current should be #enhancements good-starter-issue Good starter issue to start contributing to Teleport kubernetes-access

Comments

@Erick-Reyes
Copy link
Contributor

Erick-Reyes commented May 23, 2022 •
edited

What would you like Teleport to do?

  • We would like the option to remove/override the cluster name from the Kubernetes context. It currently uses {{ clusterName }}-{{ kubeClusterName }} as the name in the Kubernetes context.
    e.g.
CURRENT   NAME                              CLUSTER                       AUTHINFO                          NAMESPACE
*          teleport.company-mgmt          teleport.company           teleport.company-mgmt```

Instead of "teleport.company" we would like to change this to "mgmt". 

What problem does this solve?
- Customer finds this feature very useful if the context name could be overridden. An override would allow the customer to display only the most relevant information in their Kubernetes context, making it less likely that someone accidentally applies changes to the wrong context”

If a workaround exists, please include it.
- N/A
@Erick-Reyes Erick-Reyes added feature-request Used for new features in Teleport, improvements to current should be #enhancements c-pn Internal Customer Reference labels May 23, 2022
@zmb3 zmb3 added good-starter-issue Good starter issue to start contributing to Teleport kubernetes-access labels Feb 1, 2023
tigrato added a commit that referenced this issue Apr 21, 2023
@tigrato
Add option to override kube context on tsh kube login
b6f6b93 
This PR allows users to change the kubeconfig's context name when `tsh
kube login` is executed.

It allows users to override our default naming convention
`{teleport-cluster}-{kube-cluster}` and replace it with a custom name.

`tsh kube login cluster --set-context-name=ctx` overrides the context
name to `ctx`. `--set-context` cannot be executed with `--all`.

Fixes #12833
@tigrato tigrato mentioned this issue Apr 21, 2023
Merged
github-actions bot pushed a commit that referenced this issue Apr 27, 2023
@tigrato
Add option to override kube context on tsh kube login
7b180b5 
This PR allows users to change the kubeconfig's context name when `tsh
kube login` is executed.

It allows users to override our default naming convention
`{teleport-cluster}-{kube-cluster}` and replace it with a custom name.

`tsh kube login cluster --set-context-name=ctx` overrides the context
name to `ctx`. `--set-context` cannot be executed with `--all`.

Fixes #12833
github-actions bot pushed a commit that referenced this issue Apr 27, 2023
@tigrato
Add option to override kube context on tsh kube login
43fd345 
This PR allows users to change the kubeconfig's context name when `tsh
kube login` is executed.

It allows users to override our default naming convention
`{teleport-cluster}-{kube-cluster}` and replace it with a custom name.

`tsh kube login cluster --set-context-name=ctx` overrides the context
name to `ctx`. `--set-context` cannot be executed with `--all`.

Fixes #12833
tigrato added a commit that referenced this issue Apr 28, 2023
@tigrato
Add option to override kube context on tsh kube login (#25252)
cf38dbe 
This PR allows users to change the kubeconfig's context name when `tsh
kube login` is executed.

It allows users to override our default naming convention
`{teleport-cluster}-{kube-cluster}` and replace it with a custom name.

`tsh kube login cluster --set-context-name=ctx` overrides the context
name to `ctx`. `--set-context` cannot be executed with `--all`.

Fixes #12833
tigrato added a commit that referenced this issue Apr 28, 2023
@tigrato
Add option to override kube context on tsh kube login (#25253)
a958d67 
This PR allows users to change the kubeconfig's context name when `tsh
kube login` is executed.

It allows users to override our default naming convention
`{teleport-cluster}-{kube-cluster}` and replace it with a custom name.

`tsh kube login cluster --set-context-name=ctx` overrides the context
name to `ctx`. `--set-context` cannot be executed with `--all`.

Fixes #12833
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
c-pn Internal Customer Reference feature-request Used for new features in Teleport, improvements to current should be #enhancements good-starter-issue Good starter issue to start contributing to Teleport kubernetes-access
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add option to override kube context on tsh kube login gravitational/teleport
2 participants
@zmb3 @Erick-Reyes