Add CLI printer columns for machine, machinesets

[derekwaynecarr]

This adds pretty printers when rendering tables in CLI.

Machines

oc get machines -n openshift-cluster-api
NAME                                 INSTANCE              STATE     TYPE       REGION      ZONE         AGE
decarr-dev-master-0                  i-0c5c6028992720b04   running   m4.large   us-east-2   us-east-2a   4h

MachineSets

oc get machinesets -n openshift-cluster-api
NAME                           DESIRED   CURRENT   READY     AVAILABLE   AGE
decarr-dev-worker-us-east-2a   1         1         1         1           4h

[derekwaynecarr]

It is inevitable that you will want printers for each provider.

The beta is targeting AWS, so this is good for now. As we surface other providers, we may want to look at having the machine-api-operator itself install the CRDs that vary by provider so we can have pretty columns rendered with platform specific metadata.

We should do the same for machinedeployments.

When we support machine class, we want to revisit this.

/cc @enxebre @smarterclayton

[smarterclayton]

I hate machinesets columns (which are really deployment columns) but it's fine. I have open bugs upstream to make them not suck, but it's not your problem

[enxebre]

/approve

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: enxebre

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [enxebre]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[enxebre]

thanks! I added a commit on your branch to make yaml lint happy

[enxebre]

/test e2e-aws

[ingvagabund]

It is inevitable that you will want printers for each provider.

Would be great to have a clean way to do that.

The beta is targeting AWS, so this is good for now. As we surface other providers, we may want to look at having the machine-api-operator itself install the CRDs that vary by provider so we can have pretty columns rendered with platform specific metadata.

As long as the CRDs are again managed by the machine-api-operator, it is acceptable. Though, it will cause troubles when (and if) we start supporting multiple instances of an actuator inside the same cluster (a.k.a hybrid clouds).

[ingvagabund]

/lgtm

/retest

[ingvagabund]

/retest

[openshift-bot]

/retest

Please review the full test history for this PR and help us cut down flakes.

[ingvagabund]

/retest