-
Notifications
You must be signed in to change notification settings - Fork 922
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
Enhance kubectl create (Add useful flags from kubectl run e.g. replicas, labels, requests, limits, env, port etc.) #898
Comments
Related PRs: |
@armujahid there's a discussion that needs to be had about enhancing kubectl create/run and their intended goals. I've added it to the agenda for our next SIG-CLI meeting and it would be great to have you join us. Next meeting is August 12th at 9:00 AM Pacific Time. https://github.com/kubernetes/community/tree/master/sig-cli#meetings /priority awaiting-more-evidence |
@armujahid are you ok closing this after the SIG-CLI discussion? As a note of historical reference it was discussed that Will link to recording when it's uploaded. |
Sure. I would love to contribute to |
It's been some time, was anything moved forward on |
Linking https://github.com/eddiezane/kubectl-generate repo. Currently in WIP. |
kubectl create
is currently too limited.kubectl run
gave a-lot flexibility in creating deployments and jobs via command-line.We can do very little with kubectl create without editing yaml file. In my opinion it was a very bad idea to remove generators in kubectl run without providing similar functionality in
kubectl create
.What would you like to be added:
Add the functionality lost as a result of generators removal from
kubectl run
. We should be able to add labels, replicas, requests, limits or any other functionality that is supported bykubectl run
.Flags required:
Why is this needed:
The current
kubectl create
is way too limited!! It really hinders what can be done via command-line.Related issue: kubernetes/kubernetes#88888
The text was updated successfully, but these errors were encountered: