kubectl convert is deprecated

The initial kubectl convert deprecation was announced prior to release 1.13. Following the Kubernetes deprecation policy, this kubectl subcommand is now eligible to be removed in release 1.17. The following are options for next steps as this convert functionality is removed from kubectl. If you have an opinion, please add comments to this issue so that we can quickly drive consensus and make a decision on which option we will pursue.

• Convert as a Plugin
• Convert as a Binary
• Convert into the API Server
• Drop convert functionality

Convert as a Plugin

We could move the kubectl convert code into a plugin named kubectl-convert. The invocation of the plugin would mimic the current command: kubectl convert.

• Pro: Users depending on this functionality will still be able to convert resource versions.
• Pro: The command will appear similar. Naming the plugin kubectl-convert will ensure kubectl users can type the same command: kubectl convert.
• Con: The users will have to find and download this separate binary.
• Con: The plugin would have to vendor in most of the Kubernetes.

Convert as a Binary

• Pro: Users depending on this functionality will still be able to convert resource versions.
• Con: The users will have to find and download this separate binary.
• Con: The plugin would have to vendor in most of the Kubernetes.

Convert into the API Server

• Pro: Users depending on this functionality will still be able to convert resource versions.
• Pro: Convert code already lives in the API machinery.
• Con: It may take a long time to get this into the API Server.

Drop convert functionality

• Pro: This will be the simplest to implement; just remove kubectl convert subcommand code.
• Con: Users depending on this functionality will NOT be able to convert resource versions.