mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
42 lines
1.3 KiB
Plaintext
42 lines
1.3 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * installing/disconnected_install/installing-mirroring-disconnected-v2.adoc
|
|
|
|
:_mod-docs-content-type: REFERENCE
|
|
[id="oc-mirror-workflows-table_{context}"]
|
|
= Comparison of oc-mirror workflows
|
|
|
|
[role="_abstract"]
|
|
Use the following table to compare the supported use cases for the mirror-to-disk (m2d), disk-to-mirror (d2m), and mirror-to-mirror (m2m) workflows.
|
|
|
|
[%header,cols="3",cols="2,1,1",options="header",subs="quotes"]
|
|
|===
|
|
^|*Use Case*
|
|
^|*Mirror To Disk (m2d) and Disk To Mirror (d2m)*
|
|
^|*Mirror To Mirror (m2m)*
|
|
|
|
^|The target registry exists in an environment with no internet access and no external access.
|
|
^|✓
|
|
^|
|
|
|
|
^|The target registry exists in an environment with no internet access but is accessible from another machine. For example, the target registry resides in a bastion host.
|
|
^|
|
|
^|✓
|
|
|
|
^|You must move content to the disconnected environment by using a physical method, such as USB devices.
|
|
^|✓
|
|
^|
|
|
|
|
^|The workflow moves content directly to the target registry without generating an intermediate tar file.
|
|
^|
|
|
^|✓
|
|
|
|
^|The workflow uses an internal cache to resume after failures but requires additional disk space.
|
|
^|✓
|
|
^|
|
|
|
|
^|The workflow does not use a cache, restarts from the beginning after a failure, and requires no additional disk space.
|
|
^|
|
|
^|✓
|
|
|===
|