-
Notifications
You must be signed in to change notification settings - Fork 1.9k
OSDOCS-17110 CQA for Microshift #106151
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
base: main
Are you sure you want to change the base?
OSDOCS-17110 CQA for Microshift #106151
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| 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 | ||||||
| :context: microshift-access-node | ||||||
| include::_attributes/attributes-microshift.adoc[] | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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. | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
there is no other way -- and we should be putting the user goal first |
||||||
|
|
||||||
| include::modules/microshift-accessing.adoc[leveloffset=+1] | ||||||
|
|
||||||
|
|
||||||
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -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. | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
no, deployments are only discussed for rhel image systems at the edge; this is incorrect language |
||||||
|
|
||||||
| include::modules/microshift-install-rpm-before.adoc[leveloffset=+1] | ||||||
|
|
||||||
|
|
@@ -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] | ||||||
|
|
||||||
| 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. | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
this is not true; restarting microshift is HIGHLY disruptive |
||||||
|
|
||||||
| include::modules/microshift-service-starting.adoc[leveloffset=+1] | ||||||
|
|
||||||
|
|
||||||
| 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. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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] | ||
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -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. | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
microshift does not make clusters, it is a single node |
||||||
|
|
||||||
| 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. | ||||||
|
|
||||||
|
|
@@ -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"] | ||||||
| ---- | ||||||
|
|
||||||
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -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. | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
i don't think this extra sentence added anything of value; not minimalism |
||||||
|
|
||||||
| [id="microshift-configuring-volume-groups_{context}"] | ||||||
| == Configuring volume groups | ||||||
|
|
||||||
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -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. | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
|
|
||||||
| .Prerequisites | ||||||
|
|
||||||
|
|
||||||
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -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. | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
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 | ||||||
|
|
||||||
|
|
||||||
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -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. | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
microshit does not have components like openshift does |
||||||
|
|
||||||
| .Prerequisites | ||||||
|
|
||||||
|
|
||||||
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -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. | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
there is no procedure here to stop workloads |
||||||
|
|
||||||
| .Prerequisites | ||||||
|
|
||||||
|
|
||||||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
spelling is wrong, use the attribute file where it was