Improve kubectl get for the service-catalog resources

[pmorie]

As probably most people are aware, the current experience using kubectl get is not great for our resources:

• Resources lack columns by default
• Adding columns is possible but requires ugly CLI flags

This issue is intertwined with a couple of other issues; I am making this issue to break out what we want to do specifically for kubectl get in the next milestone.

[nilebox]

@pmorie have the features required to support in Service Catalog been implemented in apimachinery and kubectl already (default columns)?

[pmorie]

@nilebox I believe there are several in-progress PRs.

@luksa can you link the remaining open PRs in other projects here?

[pmorie]

Here are the dependent PRs (not including PRs to our repo):

• Handle "any value" openapi definitions properly kubernetes/kube-openapi#25
• WIP: Fix definition of RawExtension in OpenAPI schema kubernetes/kubernetes#56434
• Aggregator now re-uses the model definition that it had renamed previously kubernetes/kube-openapi#22
• Fix schema merging, so references are updated properly kubernetes/kube-openapi#24

[MHBauer]

reviewed on 2018-07-30 @jboyd01 to go find an update with current status

[MHBauer]

/assign @jboyd01

[jboyd01]

Of the PRs listed by Paul in #1634 (comment) only 56434 is still open, the others have been merged. Also #2091

@luksa

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[jberkhahn]

It seems this happened?