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

Allow user defined aliases in kubectl #18023

Closed
sils opened this issue Dec 1, 2015 · 9 comments
Closed

Allow user defined aliases in kubectl #18023

sils opened this issue Dec 1, 2015 · 9 comments
Labels
area/kubectl kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/cli Categorizes an issue or PR as relevant to SIG CLI.

Comments

@sils
Copy link
Contributor

sils commented Dec 1, 2015

Git allows me to set personal aliases which saves me a lot of typing work daily. I'd love to see this kind of possibility in kubernetes as well, that would really make my day.

@thockin
Copy link
Member

thockin commented Dec 1, 2015

I could swear this was a dup, but I can not find the previous one.

YES. I want this (but I also want standard aliases for commands like desc->describe and del->delete)

@fabioy fabioy added area/kubectl sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. kind/feature Categorizes issue or PR as related to a new feature. labels Dec 1, 2015
@lavalamp lavalamp added team/ux priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. and removed priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. labels Dec 2, 2015
@erictune erictune changed the title Allow user defined aliases Allow user defined aliases in kubectl Jan 28, 2016
@bgrant0607 bgrant0607 added help-wanted priority/backlog Higher priority than priority/awaiting-more-evidence. labels Jan 28, 2016
@bgrant0607
Copy link
Member

I like this idea, but we should move preferences out of kubeconfig before we add any more. #10693

@bgrant0607
Copy link
Member

Would also like user-defined aliases for resources (pods, etc.), which could replace the hardcoded short names.

@bgrant0607
Copy link
Member

cc @erictune

@bgrant0607
Copy link
Member

This could be a mechanism used to provide a list alias: #11210

@0xmichalis
Copy link
Contributor

@kubernetes/sig-cli-feature-requests

@k8s-ci-robot k8s-ci-robot added sig/cli Categorizes an issue or PR as relevant to SIG CLI. kind/feature Categorizes issue or PR as related to a new feature. labels Jun 11, 2017
@k8s-github-robot k8s-github-robot removed the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Jun 11, 2017
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 27, 2017
@thockin
Copy link
Member

thockin commented Dec 27, 2017

@pwittrock Keep or kill?

@bgrant0607
Copy link
Member

Not likely to happen in kubectl

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/kubectl kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/cli Categorizes an issue or PR as relevant to SIG CLI.
Projects
None yet
Development

No branches or pull requests

9 participants