Skip to content

Fix MetalLB web console install procedure based on Playwright validation #112233

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.

Sign up for GitHub

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

Open
kquinn1204 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix MetalLB web console install procedure based on Playwright validation #112233

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 6 additions & 2 deletions modules/metallb-installing-using-web-console.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,18 +21,22 @@ As a cluster administrator, you can install the MetalLB Operator by using the {p
+
You can also filter options by *Infrastructure Features*. For example, select *Disconnected* if you want to see Operators that work in disconnected environments, also known as restricted network environments.

. Click the *MetalLB Operator* tile and click *Install*.

. On the *Install Operator* page, accept the defaults and click *Install*.
+
The web console displays the *Installing Operator* page with a status update. Wait until the Operator installs before continuing.

.Verification

. To confirm that the installation is successful:

.. Navigate to the *Ecosystem* -> *Installed Operators* page.

.. Check that the Operator is installed in the `openshift-operators` namespace and that its status is `Succeeded`.
.. Check that the Operator is installed in the `metallb-system` namespace and that its status is `Succeeded`.

. If the Operator is not installed successfully, check the status of the Operator and review the logs:

.. Navigate to the *Ecosystem* -> *Installed Operators* page and inspect the `Status` column for any errors or failures.

.. Navigate to the *Workloads* -> *Pods* page and check the logs in any pods in the `openshift-operators` project that are reporting issues.
.. Navigate to the *Workloads* -> *Pods* page and check the logs in any pods in the `metallb-system` project that are reporting issues.