Introduce MachineStateController, MachineConfigNode, and MachineConfiguration

[cdoern]

This PR introduces the MachineStateController, which is the MCO's attempt to centralize state reporting. This controller focuses on reporting upgrade progressions and operator component progressions.

These two things are accomplished thorough the introduction of two new API Types:

1. MachineConfigNode

• Deals with Upgrade Progression
• One object per node

2. MachineConfiguration

• Deal with operator component progression (MCC, MCD, MCO)
• One Object per pod of the installed MCO.

This information is retrievable via oc get machineconfignodes and oc get machineconfiguration respectively.

The way we formulate this data in the MSC is through what I like to call "investigative state reporting". This entails looking at all data that could influence what state we are in, and use that to stitch together an accurate picture of what is going on. This allows the MCO to have it state reporting in a centralized location and also allows us significantly less API load. The other approach is to update these objects throughout the MCO whenever anything happens which ends up increasing API usage by a lot.

This state reporting is meant to provide the MCO team and customers with all possibly important info about the MCO's activities and is designed to have more features plugged into it in the future! The cool thing about centralization and a fairly modular system is that adding a new state is only a couple of extra lines of code/dependencies vs modifying data all over the MCO.

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cdoern

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [cdoern]

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

[inesqyx]

Manifests shall be taken out as we no longer have these yaml files:
mcc.machinestate.yaml
mcd.machinestate.yaml
upgrade.worker.machinestate.yaml
upgrade.master.machinestate.yaml
operator.machinestate.yaml
metrics.machinestate.yaml
bootstrap.machinestate.yaml

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle stale

[openshift-merge-robot]

PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closed this PR.

Details

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.