-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Data Driven Commands for Kubectl #2380
Comments
#2378 created for migrating the old keps into new template. |
/sig cli |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close |
@k8s-triage-robot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Enhancement Description
One-line enhancement description (can be used as a release note):
Data Driven Commands for Kubectl
Kubernetes Enhancement Proposal:
Many Kubectl commands make requests to specific Resource endpoints. The request bodies are populated by flags
provided by the user.
Examples:
create <resource>
set <field> <resource>
logs
Although these commands are compiled into the kubectl binary, their workflow is similar to a form on a webpage and
could be complete driven by the server providing the client with the request (endpoint + body) and a set of flags
to populate the request body.
Publishing commands as data from the server addresses cli integration with API extensions as well as client-server
version skew.
Note: No server-side changes are required for this, all Request and Response template expansion is performed on
the client side.
k/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update PR(s):Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
The text was updated successfully, but these errors were encountered: