Feature Description

• One-line feature description (can be used as a release note): kubectl get should get columns back from the server, not the client, to allow extensions to work cleanly
• Primary contact (assignee): smarterclayton
• Responsible SIGs: sig-cli, sig-api-machinery
• Design proposal link (community repo): https://github.com/kubernetes/community/blob/master/contributors/design-proposals/api-machinery/server-get.md
• KEP: https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/20190322-server-side-get-to-ga.md
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: pwittrock soltysh
• Approver (likely from SIG/area to which feature belongs): pwittrock soltysh
• Feature target (which target equals to which milestone):
  • Alpha release target (x.y): 1.8 (server API)
  • Beta release target (x.y): 1.10 (client get, server API)
  • Stable release target (x.y): 1.15 (client get, server API)

As part of the split of kubectl from close coupling with the repository, and to allow better extensibility, it should be possible for third party API extensions and CRD to provide custom output for kubectl get to avoid kubectl having to have code to interpret those resources. We will move the printing to the server side, and kubectl will retrieve results. We also wish to move describe in a future release.