Annotate manifests for single-node-developer cluster profile

[guillaumerose]

This implements phase 1 of openshift/enhancements#482

[cfergeau]

/retest

[kikisdeliveryservice]

/retest

[kikisdeliveryservice]

/approve

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: guillaumerose, kikisdeliveryservice

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 [kikisdeliveryservice]

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

[openshift-merge-robot]

@guillaumerose: The following tests failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
ci/prow/okd-e2e-aws	42b6304	link	/test okd-e2e-aws
ci/prow/e2e-aws-workers-rhel7	42b6304	link	/test e2e-aws-workers-rhel7
ci/prow/e2e-ovn-step-registry	42b6304	link	/test e2e-ovn-step-registry

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[cgwalters]

This is going to conflict with #2221 but I guess whoever merges second will just win the conflict resolution game 😉 Well to be fair to him since it was first I added lgtm.

I thought CodeReady wasn't using the MCO because it wasn't doing in-place updates? In light of openshift/enhancements#504 though perhaps that is changing?

[kikisdeliveryservice]

This was discussed in the team meeting and @runcom and @crawford are both aware said that we can merge this for 4.7 for CRC.

[runcom]

/approve
/lgtm

[kikisdeliveryservice]

ugh labelling isn't getting picked up... reported in 4-dev =(

[kikisdeliveryservice]

/skip

[guillaumerose]

@cgwalters It runs once when we bootstrap the cluster and then we disable it. But the long term goal is to keep it activated (and handle reboot, etc.).