mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
48 lines
2.5 KiB
Plaintext
48 lines
2.5 KiB
Plaintext
// Module included in the following assemblies:
|
|
// * updating/updating_a_cluster/updating_disconnected_cluster/disconnected-update-osus.adoc
|
|
|
|
:_mod-docs-content-type: PROCEDURE
|
|
[id="update-service-graph-data_{context}"]
|
|
= Creating the OpenShift Update Service graph data container image
|
|
|
|
The OpenShift Update Service requires a graph data container image, from which the OpenShift Update Service retrieves information about channel membership and blocked update edges. Graph data is typically fetched directly from the update graph data repository. In environments where an internet connection is unavailable, loading this information from an init container is another way to make the graph data available to the OpenShift Update Service. The role of the init container is to provide a local copy of the graph data, and during pod initialization, the init container copies the data to a volume that is accessible by the service.
|
|
|
|
[NOTE]
|
|
====
|
|
The oc-mirror OpenShift CLI (`oc`) plugin creates this graph data container image in addition to mirroring release images. If you used the oc-mirror plugin to mirror your release images, you can skip this procedure.
|
|
====
|
|
|
|
.Procedure
|
|
|
|
. Create a Dockerfile, for example, `./Dockerfile`, containing the following:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
FROM registry.access.redhat.com/ubi9/ubi:latest
|
|
|
|
RUN curl -L -o cincinnati-graph-data.tar.gz https://api.openshift.com/api/upgrades_info/graph-data
|
|
|
|
RUN mkdir -p /var/lib/cincinnati-graph-data && tar xvzf cincinnati-graph-data.tar.gz -C /var/lib/cincinnati-graph-data/ --no-overwrite-dir --no-same-owner
|
|
|
|
CMD ["/bin/bash", "-c" ,"exec cp -rp /var/lib/cincinnati-graph-data/* /var/lib/cincinnati/graph-data"]
|
|
----
|
|
|
|
. Use the docker file created in the above step to build a graph data container image, for example, `registry.example.com/openshift/graph-data:latest`:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ podman build -f ./Dockerfile -t registry.example.com/openshift/graph-data:latest
|
|
----
|
|
|
|
. Push the graph data container image created in the previous step to a repository that is accessible to the OpenShift Update Service, for example, `registry.example.com/openshift/graph-data:latest`:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ podman push registry.example.com/openshift/graph-data:latest
|
|
----
|
|
+
|
|
[NOTE]
|
|
====
|
|
To push a graph data image to a registry in a disconnected environment, copy the graph data container image created in the previous step to a repository that is accessible to the OpenShift Update Service. Run `oc image mirror --help` for available options.
|
|
====
|