Skip to content

Conversation

@smarterclayton
Copy link
Contributor

The machine-os-content image is injected into our CI stream containing
a snapshot of recent openshift projects (kubelet, crio, oc). To ensure
we are testing what we merge, this PR adds a new layer job to origin
that takes the current machine-os-content image and uses it as input
to a special layering Dockerfile defined in origin which injects the
version of the kubelet and oc binaries from the PR build. The
machine-os-content image is then overriden in stable, but is not
promoted using the new exclusion rule in openshift/ci-operator#254.

This will be the model for crio or any other RPM that doesn't
require special boot time changes (like ignition or the kernel would).
However, this allows us to test upgrades like they will actually
happen in the wild.

This will be merged after the ci-operator change, and after the
dockerfile merges to origin, but before the machine-config-operator
starts respecting the payload image (and causes reboots when
machine start up).

@smarterclayton
Copy link
Contributor Author

openshift/origin#21919 is a prerequisite for this merging.

@smarterclayton
Copy link
Contributor Author

@cgwalters this is approximately what the final job will look like. I need to test more extensively.

@petr-muller
Copy link
Member

/retest

@cgwalters
Copy link
Member

We probably should do https://github.com/openshift/release/issues/2750 before this.

@cgwalters
Copy link
Member

And in order to actually use this we'll need to land the MCO work: openshift/machine-config-operator#355

@petr-muller
Copy link
Member

/retest

The machine-os-content image is injected into our CI stream containing
a snapshot of recent openshift projects (kubelet, crio, oc). To ensure
we are testing what we merge, this PR adds a new layer job to origin
that takes the current machine-os-content image and uses it as input
to a special layering Dockerfile defined in origin which injects the
version of the kubelet and oc binaries from the PR build. The
machine-os-content image is then overriden in stable, but is not
promoted using the new exclusion rule in openshift/ci-operator#254.

This will be the model for crio or any other RPM that doesn't
require special boot time changes (like ignition or the kernel would).
However, this allows us to test upgrades like they will actually
happen in the wild.

This will be merged after the ci-operator change, and after the
dockerfile merges to origin, but before the machine-config-operator
starts respecting the payload image (and causes reboots when
machine start up).
@smarterclayton
Copy link
Contributor Author

/test all

@smarterclayton smarterclayton added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Feb 3, 2019
@smarterclayton smarterclayton changed the title WIP: Allow Origin PR builds in master to inject kubelet into rhcos Allow Origin PR builds in master to inject kubelet into rhcos Feb 3, 2019
@openshift-merge-robot openshift-merge-robot merged commit 5df55fc into openshift:master Feb 3, 2019
@smarterclayton smarterclayton deleted the inject_into_rhcos branch April 24, 2019 14:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants