WIP: Embed rhcos*.json as /bootimage/rhcos*.json in container image

[cgwalters]

This is intended as a short term tweak on the (long) road
to openshift/enhancements#201

See specifically this subthread:
openshift/enhancements#201 (comment)
And openshift/enhancements#201 (comment)

TL;DR we want oc to be the frontend to this data, via something like
oc adm release info --bootimage-json or so, and not openshift-install.

We want to move towards having the data as part of the release image.
But the installer will have RHCOS pinned for the near future because
of the bootstrap node - we need an RHCOS for that too.

And it's going to be very problematic to have "two sources of truth"
for RHCOS even temporarily.

This small change puts the RHCOS json inside the installer container
image which is already part of the release payload and built from
this repository; then we can patch oc to have oc adm bootimages --json
which would do the equivalent of:
oc image extract /bootimage:. $(oc adm release info --image-for=installer))

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign abhinavdahiya
You can assign the PR to them by writing /assign @abhinavdahiya in a comment when ready.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[openshift-ci-robot]

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

Test name	Commit	Details	Rerun command
ci/prow/e2e-ovirt	09d3968	link	/test e2e-ovirt
ci/prow/e2e-crc	09d3968	link	/test e2e-crc
ci/prow/e2e-openstack	09d3968	link	/test e2e-openstack

Full PR test history. Your PR dashboard.

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 can probably wait for 4.7, just trying to make a bit of forward progress on this.

[cgwalters]

I just noticed that the UPI container already does this:
COPY --from=builder /go/src/github.com/openshift/installer/data/data/rhcos.json /var/lib/openshift-install/rhcos.json

[wking]

UPI image should be CI-only, not part of official releases. I hope :p

[abhinavdahiya]

@cgwalters what's our plan, if any, to move ahead with 201 for 4.7 ?

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

@openshift-bot: Closed this PR.

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.