Enhancement Description
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.
Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
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>logsAlthough 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.