KEP proposal for extended support for kubectl create command

[domenico muscillo]

Hello everyone, i have recently achieved the CKA and during the exam i was thinking that i could solve many problems in half the time if there was a way not to rely on editing with vim the manifests. I am a fan of kubectl tool (infact i am refusing to use any dashboard and rely just on the terminal to operate on my clusters) and i wonder why the kubectl create command works just on a specific set of resources whence the kubectl describe command can show arbitrary informations about resources based on their CRDs definitions. I would love to create any custom resource and specify its configuration parameters in a single line with the CLI. This would make scripts using kubectl much more clean and free users from using yaml (given the contempt many people feel against this file format). I do not know if this classifies as a KEP and i apologize in advance in case i have skipped some steps with writing this in the mailing list.

Happy to hear some thoughts about it!

[Marly Salazar]

Hi,

We already support this via the plugin route today. If you would like to extend the ecosystem of available plugins to include more types of resources we would gladly accept these in our plugin manager krew. Please find more details about the support this at the link below:

https://github.com/kubernetes/enhancements/tree/master/keps/sig-cli/3638-kubectl-plugin-subcommands

At this time we are not interested in extending the create command further in the main kubectl codebase due to the significant increase of the support burden of maintaining the large number of resources and flags that would be required to extend what is available today.

Thank you,

Marly Salazar

On Thu, Feb 19, 2026 at 5:57 AM domenico muscillo <domenicom...@gmail.com> wrote:

Hello everyone, i have recently achieved the CKA and during the exam i was thinking that i could solve many problems in half the time if there was a way not to rely on editing with vim the manifests. I am a fan of kubectl tool (infact i am refusing to use any dashboard and rely just on the terminal to operate on my clusters) and i wonder why the kubectl create command works just on a specific set of resources whence the kubectl describe command can show arbitrary informations about resources based on their CRDs definitions. I would love to create any custom resource and specify its configuration parameters in a single line with the CLI. This would make scripts using kubectl much more clean and free users from using yaml (given the contempt many people feel against this file format). I do not know if this classifies as a KEP and i apologize in advance in case i have skipped some steps with writing this in the mailing list.

Happy to hear some thoughts about it!

--
You received this message because you are subscribed to the Google Groups "sig-cli" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sig-cli+u...@kubernetes.io.
To view this discussion visit https://groups.google.com/a/kubernetes.io/d/msgid/sig-cli/bf93db5c-367c-4527-825e-2ae9985e1f20n%40kubernetes.io.