Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MCO-392: Start using rhel-coreos image rather than machine-os-content #135

Merged
merged 1 commit into from
Nov 9, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/driver_toolkit_imagestream.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,5 +8,5 @@ In order to generate such imagestream during the cluster installation, there are

* DTK: add an [templated imagestream](../manifests/01-openshift-imagestream.yaml) to the payload.
* ART: adding that imagestream to the cluster deployment (templeted) by running `oc adm release new ...`.
* OC: Owning the code for `oc adm release new …` which will scrape the [machine-os-content](https://github.com/openshift/machine-config-operator/blob/master/docs/OSUpgrades.md#os-updates).
* MCO: owns the machine-os-content.
* OC: Owning the code for `oc adm release new …` which will scrape the [rhel-coreos image](https://github.com/openshift/machine-config-operator/blob/master/docs/OSUpgrades.md#os-updates).
* MCO: owns the `rhel-coreos` image.
4 changes: 2 additions & 2 deletions manifests/image-references
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ spec:
from:
kind: DockerImage
name: example.com/image-reference-placeholder:driver-toolkit
- name: machine-os-content
- name: rhel-coreos
from:
kind: DockerImage
name: registry.svc.ci.openshift.org/openshift:machine-os-content
name: example.com/image-reference-placeholder:rhel-coreos