Added basic status to CR{D}

[jpkrohling]

This PR adds a new JaegerPhase type, added to the JaegerStatus. When running kubectl get jaegers, this is what is shown now:

$ kubectl get jaegers
NAME                         STATUS    VERSION
jaeger-all-in-one-inmemory   Running   1.15.1

When getting the output as YAML for a specific instance, here's the output:

$ kubectl get jaegers jaeger-all-in-one-inmemory -o yaml | tail
      resources: {}
      schedule: '*/30 * * * *'
    options: {}
    type: memory
  strategy: allinone
  ui:
    options: {}
status:
  phase: Running
  version: 1.15.1

And here's how it shows up in OLM:

Note that the Version field isn't being showed in OLM yet.

This is related to #259, although it won't close it, as we might want to keep that open to discuss further status fields in the future.

Signed-off-by: Juraci Paixão Kröhling [email protected]

[jpkrohling]

According to people on the #forum-operator-fw in the CoreOS slack, the Version column in the UI shows the value of .Spec.Version. Note that we have a .Status.Version, not .Spec. I'm still trying to confirm what this field refers to, as we do not want the version field to be part of the spec (as it's managed by the operator, not defined by the user).

[jpkrohling]

This PR is now ready to be reviewed. There's still one thing that could be better: when creating a CR, it would be good to have the initial state as "Pending". But to do that, we have to persist the status and finish the reconciliation loop, as this change itself will trigger an update. I decided to not add the Pending state, and have only a Failed or Running.

[jpkrohling]

PR updated.

[objectiser]

LGTM