This is a tracker for the work items to bring server-side printing to beta in 1.10:

Server:

• move the Table API to beta
• put table API behind feature gate
• determine whether to have a shorthand mime-type for table (application/json+meta+v1+Table) or similar
• Add better E2E tests that verify that all APIs implement the server side printer ( Add missing table converters for server side printing  #60580)
• Add a unit test that verifies everyone implements printer ( Add missing table converters for server side printing  #60580)
• Move the OpenAPI column rendering for CRD to the server in the CRD implementation Implement a stub server printer for CRDs #60269
• Do a final pass on the default metadata renderer (the generic one)
• Add a "example fuzzer" that returns a Table filled with all the values we could anticipate so that it's easy to test client impls
• Review the Table API with a JS web console user
• Stretch goal: look at a CSV mime type that uses table printing
• Provide a table implementation for services Refactor service storage to remove registry wrapper #59510

Client:

• Have kubectl get fetch table resources and pass them into the printer (with fallback to client side printing if the server doesn't return a Table) (Update get.go to use server-side printing #55637)
• Have a flag to disable server side rendering that defaults to false
• Add client side tests that validate server side printing can be bypassed
• Sorting and printing should be using the table but with full objects returned via the print API (?includeObject=Object) and then doing the sort on nested, as should custom columns.
• We should also test service-catalog resources with Table printers. I have made a note of this here.

The continuation of this work in 1.11 is in #60712.