Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions microshift_install_rpm/microshift-access-node.adoc
Original file line number Diff line number Diff line change
@@ -1,13 +1,13 @@
:_mod-docs-content-type: ASSEMBLY
[id="microshift-access-node"]
include::_attributes/attributes-microshift.adoc[]
= Accessing the {microshift-short} node with oc
= Accessing the Microshift node with oc
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
= Accessing the Microshift node with oc
= Accessing the MicroShift node with oc

spelling is wrong, use the attribute file where it was

:context: microshift-access-node
include::_attributes/attributes-microshift.adoc[]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nope, leave the attribute where it was


toc::[]

[role="_abstract"]
Access a {microshift-short} node by using the {oc-first}.
Use the {oc-first} command-line tool to access your {microshift-short} node. This connection enables you to manage cluster resources, debug deployments, and verify system health directly from the command line.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Use the {oc-first} command-line tool to access your {microshift-short} node. This connection enables you to manage cluster resources, debug deployments, and verify system health directly from the command line.
Access your {microshift-short} node by using the {oc-first}. This connection enables you to manage cluster resources, debug deployments, and verify system health.

there is no other way -- and we should be putting the user goal first
i believe the oc first attribute includes "CLI"


include::modules/microshift-accessing.adoc[leveloffset=+1]

Expand Down
5 changes: 3 additions & 2 deletions microshift_install_rpm/microshift-install-rpm.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,8 @@ include::_attributes/attributes-microshift.adoc[]

toc::[]

You can install {microshift-short} from an RPM package on a machine with a supported version of {op-system-base-full}.
[role="_abstract"]
Install {microshift-short} from an RPM package to deploy the service on a supported version of {op-system-base-full}. This method uses standard package management tools to help you manage the installation and future updates.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Install {microshift-short} from an RPM package to deploy the service on a supported version of {op-system-base-full}. This method uses standard package management tools to help you manage the installation and future updates.
Install {microshift-short} from an RPM package on a supported version of {op-system-base-full}. This method uses standard package management tools to help you manage the installation and future updates.

no, deployments are only discussed for rhel image systems at the edge; this is incorrect language
what is happening here is that a dev engineer is installing microshift on rhel so that apps can be built for it


include::modules/microshift-install-rpm-before.adoc[leveloffset=+1]

Expand All @@ -18,7 +19,7 @@ include::modules/microshift-install-rpms.adoc[leveloffset=+1]
[role="_additional-resources"]
== Additional resources
* xref:../microshift_install_get_ready/microshift-fips.adoc#microshift-fips[Using FIPS mode with {microshift-short}]
* Download the link:https://console.redhat.com/openshift/install/pull-secret[pull secret] from the Red Hat Hybrid Cloud Console
* link:https://console.redhat.com/openshift/install/pull-secret[pull secret]
* xref:../microshift_configuring/microshift-using-config-yaml.adoc#microshift-using-config-yaml[Customizing {microshift-short} by using the configuration file]
* link:https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/interactively_installing_rhel_over_the_network/customizing-the-system-in-the-installer_rhel-installer#manual-partitioning_customizing-the-system-in-the-installer[Configuring manual partitioning]
* link:https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/configuring_and_managing_logical_volumes/overview-of-logical-volume-management_configuring-and-managing-logical-volumes[Overview of logical volume management]
Expand Down
6 changes: 4 additions & 2 deletions microshift_install_rpm/microshift-stop-start.adoc
Original file line number Diff line number Diff line change
@@ -1,12 +1,14 @@
:_mod-docs-content-type: ASSEMBLY
[id="microshift-stop-start"]
include::_attributes/attributes-microshift.adoc[]
= Stopping and starting {microshift-short}
include::_attributes/attributes-microshift.adoc[]

:context: microshift-stop-start

toc::[]

You can stop or start {microshift-short} for a variety of reasons, including a fresh installation, adding optional RPM packages, and troubleshooting.
[role="_abstract"]
Stop or start the {microshift-short} service to troubleshoot issues, perform fresh installations, or add optional RPM packages. Controlling the service state enables configuration changes to take effect and simplifies system maintenance.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Stop or start the {microshift-short} service to troubleshoot issues, perform fresh installations, or add optional RPM packages. Controlling the service state enables configuration changes to take effect and simplifies system maintenance.
Stop or start the {microshift-short} service to troubleshoot issues, perform fresh installations, or add optional RPM packages. Controlling the service state enables configuration changes to take effect.

this is not true; restarting microshift is HIGHLY disruptive


include::modules/microshift-service-starting.adoc[leveloffset=+1]

Expand Down
6 changes: 4 additions & 2 deletions microshift_install_rpm/microshift-uninstall-rpm.adoc
Original file line number Diff line number Diff line change
@@ -1,11 +1,13 @@
:_mod-docs-content-type: ASSEMBLY
[id="microshift-uninstall-rpm"]
include::_attributes/attributes-microshift.adoc[]
= Uninstalling {microshift-short}
include::_attributes/attributes-microshift.adoc[]

:context: microshift-uninstall-rpm

toc::[]

Before you uninstall {microshift-short}, clean up all the {microshift-short} data and configuration by running the `microshift-cleanup-data` script.
[role="_abstract"]
Uninstall {microshift-short} to remove the software from your system. You must run the `microshift-cleanup-data` script to delete all data and configuration files before you remove the packages.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you actually said the opposite of what was here; please check with @ggiguash if your language is still correct


include::modules/microshift-uninstall-microshift-rpms.adoc[leveloffset=+1]
2 changes: 1 addition & 1 deletion modules/microshift-accessing-node-locally.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@
= Accessing the {microshift-short} node locally

[role="_abstract"]
Use the following procedure to access the {microshift-short} node locally by using a `kubeconfig` file.
Access the {microshift-short} node locally by using a kubeconfig file to manage your cluster directly from the host machine. This configuration verififies that the cluster status and perform administrative tasks without external network dependencies.

.Prerequisites

Expand Down
2 changes: 1 addition & 1 deletion modules/microshift-accessing-node-open-firewall.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@
= Opening the firewall for remote access to the {microshift-short} node

[role="_abstract"]
You must open the firewall before a workstation user can access the {microshift-short} node remotely.
Open the firewall on the {microshift-short} host to enable remote access from a separate workstation. This configuration allows a remote user to connect to the node and helps ensure they can access the Kubernetes API server.

For this procedure, `user@microshift` is the user on the {microshift-short} host machine and is responsible for setting up that machine so that it can be accessed by a remote user on a separate workstation.

Expand Down
4 changes: 2 additions & 2 deletions modules/microshift-accessing-node-remotely.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@
= Accessing the {microshift-short} node remotely

[role="_abstract"]
Access the {microshift-short} service from a remote location by using a `kubeconfig` file.
To manage your cluster from a local workstation, access the {microshift-short} service remotely by using a kubeconfig file. You can now control the cluster without logging in to the host machine.
Copy link
Contributor

@ShaunaDiaz ShaunaDiaz Feb 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
To manage your cluster from a local workstation, access the {microshift-short} service remotely by using a kubeconfig file. You can now control the cluster without logging in to the host machine.
Access the {microshift-short} service remotely by using a kubeconfig file.

microshift does not make clusters, it is a single node
microshift is deployed on edge devices; there barely any interaction with the node compared with an OCP cluster


The `user@workstation` login is used to access the host machine remotely. The `<user>` value in the procedure is the name of the user that `user@workstation` logs in with to the {microshift-short} host.

Expand Down Expand Up @@ -37,7 +37,7 @@ The `user@workstation` login is used to access the host machine remotely. The `<
+
Replace the value, _<{microshift-short}_hostname>_, with the either the name or the IP address of the host running {microshift}.

. As `user@workstation`, copy the generated `kubeconfig` file that contains the hostname or IP address you want to connect to from the {op-system-base} machine running {microshift-short} to your local machine by running the following command:
. As `user@workstation`, copy the generated `kubeconfig` file that has the hostname or IP address you want to connect to from the {op-system-base} machine running {microshift-short} to your local machine by running the following command:
+
[source,terminal,subs="+quotes"]
----
Expand Down
2 changes: 1 addition & 1 deletion modules/microshift-accessing.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -12,4 +12,4 @@ Access the {microshift-short} service by using the {oc-first}.

* You can access the node from either the same machine running the {microshift-short} service or from a remote location.
* You can use this access to observe and administer workloads.
* When using the following steps, choose the `kubeconfig` file that contains the hostname or IP address you want to connect to and place it in the relevant directory.
* When using the following steps, choose the `kubeconfig` file that has the hostname or IP address you want to connect to and place it in the relevant directory.
3 changes: 2 additions & 1 deletion modules/microshift-install-rpm-before.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,8 @@
[id="microshift-install-rpm-before_{context}"]
= Before installing {microshift-short} from an RPM package

Preparation of the host machine is recommended before installing {microshift-short} for memory configuration and FIPS mode.
[role="_abstract"]
Prepare your host machine to handle memory configuration and FIPS mode requirements before installing {microshift-short}. Proper preparation ensures a successful installation.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Prepare your host machine to handle memory configuration and FIPS mode requirements before installing {microshift-short}. Proper preparation ensures a successful installation.
Prepare your host machine to handle memory configuration and FIPS mode requirements before installing {microshift-short}.

i don't think this extra sentence added anything of value; not minimalism


[id="microshift-configuring-volume-groups_{context}"]
== Configuring volume groups
Expand Down
3 changes: 2 additions & 1 deletion modules/microshift-install-rpm-preparing.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,8 @@
[id="microshift-install-rpm-preparing_{context}"]
= Preparing to install {microshift-short} from an RPM package

Configure your {op-system-base} machine to have a logical volume manager (LVM) volume group (VG) with sufficient capacity for the persistent volumes (PVs) of your workload.
[role="_abstract"]
To support the persistent volumes of your workload, configure a logical volume manager (LVM) volume group on your machine. You can adjust the capacity settings so that your system has enough space for your applications.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
To support the persistent volumes of your workload, configure a logical volume manager (LVM) volume group on your machine. You can adjust the capacity settings so that your system has enough space for your applications.
To support the persistent volumes (PVs) of your workload, configure a logical volume manager (LVM) volume group (VG) on your machine. You can adjust the capacity settings so that your system has enough space for your applications.


.Prerequisites

Expand Down
3 changes: 2 additions & 1 deletion modules/microshift-install-rpms.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,8 @@
[id="installing-microshift-from-rpm-package_{context}"]
= Installing {microshift-short} from an RPM package

Use the following procedure to install {microshift-short} from an RPM package.
[role="_abstract"]
Install {microshift-short} from an RPM package to deploy the software on your Red Hat Enterprise Linux system. This method manages updates by using standard subscription tools and maintains a supported configuration by locking your operating system version.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Install {microshift-short} from an RPM package to deploy the software on your Red Hat Enterprise Linux system. This method manages updates by using standard subscription tools and maintains a supported configuration by locking your operating system version.
Install {microshift-short} from an RPM package on your {use the attribute here} system. This method manages updates by using standard subscription tools and maintains a supported configuration by locking your operating system version.

i don't know what subscription tools you mean here: microshift does not use update channels like openshift; my guess is that your change is inaccurate


.Prerequisites

Expand Down
3 changes: 2 additions & 1 deletion modules/microshift-service-starting.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,8 @@
[id="starting-microshift_service_{context}"]
= Starting the {microshift-short} service

Use the following procedure to start the {microshift-short} service.
[role="_abstract"]
Start the {microshift-short} service to activate your cluster and prepare it for running workloads. This step verifies that all necessary components are running and ready to accept applications.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Start the {microshift-short} service to activate your cluster and prepare it for running workloads. This step verifies that all necessary components are running and ready to accept applications.
Start the {microshift-short} service to activate your node and prepare it for running workloads.

microshit does not have components like openshift does
also, depending on where you use this module, optional add-ons might or might not be ready


.Prerequisites

Expand Down
3 changes: 2 additions & 1 deletion modules/microshift-service-stopping.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,8 @@
[id="stopping-microshift-service_{context}"]
= Stopping the {microshift-short} service

Use the following procedure to stop the {microshift-short} service.
[role="_abstract"]
Stop the {microshift-short} service and all running workloads to safely halt cluster operations. This allows maintenance or troubleshooting to be performed without active processes interfering and achieving a complete system shutdown.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Stop the {microshift-short} service and all running workloads to safely halt cluster operations. This allows maintenance or troubleshooting to be performed without active processes interfering and achieving a complete system shutdown.
Use the following procedure to stop the {microshift-short} service.

there is no procedure here to stop workloads
and the rest is inaccurate; a complete system shutdown is not the goal of this procedure (and would need to include any resident rhel system)


.Prerequisites

Expand Down
8 changes: 6 additions & 2 deletions modules/microshift-uninstall-microshift-rpms.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,9 @@
[id="microshift-uninstall-microshift-rpms_{context}"]
= Uninstalling {microshift-short} from an RPM package

[role="_abstract"]
Uninstall the {microshift-short} RPM package to remove the software and reset your system. This process deletes all data, pods, and configurations to help ensure a clean environment for future deployments.

.Prerequisites

* You are logged into {microshift-short} as an administrator with root-user access.
Expand All @@ -18,9 +21,10 @@
+
[source,terminal,subs="+quotes"]
----
$ sudo microshift-cleanup-data --all <1>
$ sudo microshift-cleanup-data --all
----
<1> When you run the script with the `--all` argument, you perform the following clean up actions:
+
When you run the script with the `--all` argument, you perform the following clean up actions:

* Stop and disable all {microshift-short} services
* Delete all {microshift-short} pods
Expand Down