You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* You reviewed details about the xref:../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update] processes.
13
15
* You read the documentation on xref:../../installing/installing-preparing.adoc#installing-preparing[selecting a cluster installation method and preparing it for users].
== Installing {product-title} with the Agent-based Installer
20
+
21
+
The following procedures deploy a single-node {product-title} in a disconnected environment. You can use these procedures as a basis and modify according to your requirements.
* See xref:../../installing/installing_bare_metal_ipi/ipi-install-installation-workflow.adoc#ipi-install-installation-workflow[Deploying with dual-stack networking].
20
-
* See xref:../../installing/installing_bare_metal_ipi/ipi-install-installation-workflow.adoc#ipi-install-installation-workflow[Configuring the install-config yaml file].
33
+
* See xref:../../installing/installing_bare_metal_ipi/ipi-install-installation-workflow.adoc#modifying-install-config-for-dual-stack-network_ipi-install-installation-workflow[Deploying with dual-stack networking].
34
+
* See xref:../../installing/installing_bare_metal_ipi/ipi-install-installation-workflow.adoc#configuring-the-install-config-file_ipi-install-installation-workflow[Configuring the install-config yaml file].
21
35
* See xref:../../installing/installing_bare_metal/installing-restricted-networks-bare-metal.adoc#installation-three-node-cluster_installing-restricted-networks-bare-metal[Configuring a three-node cluster] to deploy three-node clusters in bare metal environments.
22
36
* See xref:../../installing/installing_with_agent_based_installer/preparing-to-install-with-agent-based-installer.adoc#root-device-hints_preparing-to-install-with-agent-based-installer[About root device hints].
23
37
* See link:https://nmstate.io/examples.html[NMState state examples].
= Installing {product-title} with the Agent-based Installer
6
+
[id="installing-ocp-agent-boot_{context}"]
7
+
= Creating and booting the agent image
8
8
9
-
The following procedure deploys a single-node {product-title} in a disconnected environment. You can use this procedure as a basis and modify according to your requirements.
9
+
Use this procedure to boot the agent image on your machines.
10
10
11
11
.Procedure
12
12
13
-
. Log in to the {product-title} web console using your login credentials.
14
-
15
-
. Navigate to link:https://console.redhat.com/openshift/create/datacenter[Datacenter].
16
-
+
17
-
image::agent_install.png[]
18
-
19
-
. Click *Run Agent-based Installer locally*. You are directed to the *Install {product-title} on Bare Metal locally with Agent* page.
20
-
21
-
. Optional: Alternatively, you can also click *Bare Metal (x86_64)* on the *Select an {product-title} cluster type to create* page. You are directed to the *Create an {product-title} Cluster: Bare Metal* page.
22
-
Then, select *Local Agent-based* to go to the *Install {product-title} on Bare Metal locally with Agent* page.
23
-
+
24
-
image::agent_install_bare_metal.png[]
25
-
26
-
. Select the operating system and architecture.
27
-
28
-
. Click *Download Installer* to download and extract the install program.
29
-
30
-
. You can either download or copy the pull secret by clicking on *Download pull secret* or *Copy pull secret*.
31
-
32
-
. Click *Download command-line tools* and place the `openshift-install` binary in a directory that is on your `PATH`.
33
-
34
13
. Install `nmstate` dependency by running the following command:
35
14
+
36
15
[source,terminal]
@@ -66,7 +45,7 @@ compute:
66
45
name: worker
67
46
replicas: 0
68
47
controlPlane:
69
-
architecture: amd64
48
+
architecture: amd64
70
49
hyperthreading: Enabled
71
50
name: master
72
51
replicas: 1
@@ -90,7 +69,7 @@ sshKey: |
90
69
----
91
70
+
92
71
<1> Specify the system architecture, valid values are `amd64` and `arm64`.
93
-
<2> Required. Specify your cluster name.
72
+
<2> Required. Specify your cluster name.
94
73
<3> State the cluster network plugin to install. The supported values are `OVNKubernetes` and `OpenShiftSDN`. The default value is `OVNKubernetes`.
95
74
<4> Specify your pull secret.
96
75
<5> Specify your ssh public key.
@@ -104,6 +83,9 @@ If you set the platform to `vSphere` or `baremetal`, you can configure IP addres
NOTE: Red Hat Enterprise Linux CoreOS (RHCOS) supports multipathing on the primary disk, allowing stronger resilience to hardware failure to achieve higher host availability. Multipathing is enabled by default in the agent ISO image, with a default `/etc/multipath.conf` configuration.
194
174
195
175
. Boot the `agent.x86_64.iso` or `agent.aarch64.iso` image on the bare metal machines.
196
-
197
-
. Optional: To know when the bootstrap host (which is the rendezvous host) reboots, run the following command:
INFO To access the cluster as the system:admin user when using 'oc', run
237
-
INFO export KUBECONFIG=/home/core/installer/auth/kubeconfig
238
-
INFO Access the OpenShift web-console here: https://console-openshift-console.apps.sno-cluster.test.example.com
239
-
----
240
-
241
-
242
-
[NOTE]
243
-
====
244
-
If you are using the optional method of ZTP manifests, you can configure IP address endpoints for cluster nodes through the `AgentClusterInstall.yaml` file in three ways:
= Verifying that the current installation host can pull release images
8
+
9
+
After you boot the agent image and network services are made available to the host, the agent console application performs a pull check to verify that the current host can retrieve release images.
10
+
11
+
If the primary pull check passes, you can quit the application to continue with the installation. If the pull check fails, the application performs additional checks, as seen in the `Additional checks` section of the TUI, to help you troubleshoot the problem. A failure for any of the additional checks is not necessarily critical as long as the primary pull check succeeds.
12
+
13
+
If there are host network configuration issues that might cause an installation to fail, you can use the console application to make adjustments to your network configurations.
14
+
15
+
[IMPORTANT]
16
+
====
17
+
If the agent console application detects host network configuration issues, the installation workflow will be halted until the user manually stops the console application and signals the intention to proceed.
18
+
====
19
+
20
+
.Procedure
21
+
22
+
. Wait for the agent console application to check whether or not the configured release image can be pulled from a registry.
23
+
24
+
. If the agent console application states that the installer connectivity checks have passed, wait for the prompt to time out to continue with the installation.
25
+
+
26
+
[NOTE]
27
+
====
28
+
You can still choose to view or change network configuration settings even if the connectivity checks have passed.
29
+
30
+
However, if you choose to interact with the agent console application rather than letting it time out, you must manually quit the TUI to proceed with the installation.
31
+
====
32
+
33
+
. If the agent console application checks have failed, which is indicated by a red icon beside the `Release image URL` pull check, use the following steps to reconfigure the host's network settings:
34
+
35
+
.. Read the `Check Errors` section of the TUI.
36
+
This section displays error messages specific to the failed checks.
37
+
+
38
+
image::agent-tui-home.png[The home screen of the agent console application displaying check errors, indicating a failed check]
39
+
40
+
.. Select *Configure network* to launch the NetworkManager TUI.
41
+
42
+
.. Select *Edit a connection* and select the connection you want to reconfigure.
43
+
44
+
.. Edit the configuration and select *OK* to save your changes.
45
+
46
+
.. Select *Back* to return to the main screen of the NetworkManager TUI.
47
+
48
+
.. Select *Activate a Connection*.
49
+
50
+
.. Select the reconfigured network to deactivate it.
51
+
52
+
.. Select the reconfigured network again to reactivate it.
53
+
54
+
.. Select *Back* and then select *Quit* to return to the agent console application.
55
+
56
+
.. Wait at least five seconds for the continuous network checks to restart using the new network configuration.
57
+
58
+
.. If the `Release image URL` pull check succeeds and displays a green icon beside the URL, select *Quit* to exit the agent console application and continue with the installation.
INFO To access the cluster as the system:admin user when using 'oc', run
53
+
INFO export KUBECONFIG=/home/core/installer/auth/kubeconfig
54
+
INFO Access the OpenShift web-console here: https://console-openshift-console.apps.sno-cluster.test.example.com
55
+
----
56
+
57
+
58
+
[NOTE]
59
+
====
60
+
If you are using the optional method of ZTP manifests, you can configure IP address endpoints for cluster nodes through the `AgentClusterInstall.yaml` file in three ways:
0 commit comments