mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
39 lines
3.1 KiB
Plaintext
39 lines
3.1 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * microshift_install_get_ready/microshift-install-get-ready.adoc
|
|
|
|
:_mod-docs-content-type: CONCEPT
|
|
[id="microshift-install-rhel-types_{context}"]
|
|
= {op-system-base} installation types
|
|
|
|
Choose the best {op-system-base-full} installation type based on where you want to run your node and what your applications need to do. For the best results, apply the following principles:
|
|
|
|
* For every installation target, you must configure both the operating system and {microshift-short}.
|
|
* Consider your application storage needs, networking for node or application access, and your authentication and security requirements.
|
|
* Understand the differences between the {op-system-base} installation types, including the support scope of each, and the tools used.
|
|
|
|
[id="microshift-get-ready-install-rpm_{context}"]
|
|
== Using RPMs, or package-based installation
|
|
|
|
This simple installation type uses a basic command to install {microshift-short} on an existing {op-system-base} machine. Basic CLI tools are required for this installation type.
|
|
|
|
[id="microshift-get-ready-install-rhel-image-based_{context}"]
|
|
== {op-system-base} image-based installations
|
|
|
|
Image-based installation types involve creating an `rpm-ostree`-based, immutable version of {op-system-base} that is optimized for edge deployment.
|
|
|
|
* {op-system-ostree} can be deployed to the edge in production environments. You can use this installation type where network connections are present, restricted, or completely offline, depending on the local environment.
|
|
|
|
* Image mode for {op-system-base} is based on OCI container images and bootable containers. See the following link for an introduction to bootc technology:
|
|
|
|
** link:https://developers.redhat.com/articles/2024/09/24/bootc-getting-started-bootable-containers[bootc: Getting started with bootable containers]
|
|
|
|
When choosing an image-based installation, consider whether the installation target is intended to be in an offline or networked state, where you plan to build system images, and how you plan to load your {op-system-bundle}. Use the following scenarios as general guidance:
|
|
|
|
* If you build either a fully self-contained {op-system-ostree} or an image mode for {op-system-base} ISO outside a disconnected environment, and then install the ISO locally on your edge devices, you likely do not need an RPM repository or a mirror registry.
|
|
* If you build an ISO outside a disconnected environment that does not include the container images, but consists of only the RPMs, you need a mirror registry inside your disconnected environment. You use your mirror registry to pull container images.
|
|
* If you build images inside a disconnected environment, or use package-based installations, you need both a mirror registry and a local RPM mirror repository. You can use either the {op-system-base} reposync utility or Red{nbsp}Hat Satellite for advanced use cases. See the following links for more information:
|
|
|
|
** link:https://access.redhat.com/solutions/7019225[Creating a local mirror of the latest update for {op-system-base} without using Satellite Server]
|
|
** link:https://www.redhat.com/en/technologies/management/satellite[Red{nbsp}Hat Satellite]
|