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
<1> Replace `<hosted_cluster_name>` with your hosted cluster.
58
-
<2> Replace `<hosted_cluster_name>` with your hosted cluster. Replace `<hosted_cluster_namespace>` with the name of your hosted cluster namespace.
59
-
<3> Specify the password of the baseboard management controller (BMC) in Base64 format.
60
-
<4> Specify the user name of the BMC in Base64 format.
61
-
<5> Replace `<hosted_cluster_name>` with your hosted cluster. The `infraenvs.agent-install.openshift.io` field serves as the link between the Assisted Installer and the `BareMetalHost` objects.
62
-
<6> Replace `<hosted_cluster_name>` with your hosted cluster. The `bmac.agent-install.openshift.io/hostname` field represents the node name that is adopted during deployment.
63
-
<7> The `automatedCleaningMode` field prevents the node from being erased by the Metal3 Operator.
64
-
<8> The `disableCertificateVerification` field is set to `true` to bypass certificate validation from the client.
65
-
<9> Replace `<hosted_cluster_name>` with your hosted cluster. The `address` field denotes the BMC address of the worker node.
66
-
<10> Replace `<hosted_cluster_name>` with your hosted cluster. The `credentialsName` field points to the secret where the user and password credentials are stored.
67
-
<11> The `bootMACAddress` field indicates the interface MAC address that the node starts from.
68
-
<12> The `online` field defines the state of the node after the `BareMetalHost` object is created.
57
+
where:
58
+
59
+
<hosted_cluster_name>:: Specifies the name of your hosted cluster.
60
+
61
+
<hosted_cluster_namespace>:: Specifies the name of your hosted cluster namespace.
62
+
63
+
password:: Specifies the password of the baseboard management controller (BMC) in Base64 format.
64
+
65
+
username:: Specifies the user name of the BMC in Base64 format.
66
+
67
+
infraenvs.agent-install.openshift.io:: Serves as the link between the Assisted Installer and the `BareMetalHost` objects.
68
+
69
+
bmac.agent-install.openshift.io/hostname:: Represents the node name that is adopted during deployment.
70
+
71
+
automatedCleaningMode:: Prevents the node from being erased by the Metal3 Operator.
72
+
73
+
disableCertificateVerification:: Is set to `true` to bypass certificate validation from the client.
74
+
75
+
address:: Denotes the BMC address of the worker node.
76
+
77
+
credentialsName:: Points to the secret where the user and password credentials are stored.
78
+
79
+
bootMACAddress:: Indicates the interface MAC address that the node starts from.
80
+
81
+
online:: Defines the state of the node after the `BareMetalHost` object is created.
69
82
70
83
. Deploy the `BareMetalHost` object by entering the following command:
Copy file name to clipboardExpand all lines: modules/hcp-dc-infraenv.adoc
+11-8Lines changed: 11 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@
6
6
[id="hcp-dc-infraenv_{context}"]
7
7
= Creating an InfraEnv resource for the hosted cluster
8
8
9
-
The `InfraEnv` resource is an Assisted Service object that includes essential details, such as the `pullSecretRef` and the `sshAuthorizedKey`. Those details are used to create the Red Hat Enterprise Linux CoreOS (RHCOS) boot image that is customized for the hosted cluster.
9
+
The `InfraEnv` resource is an Assisted Service object that includes essential details, such as the `pullSecretRef` and the `sshAuthorizedKey`. Those details are used to create the {op-system-first} boot image that is customized for the hosted cluster.
10
10
11
11
You can host more than one `InfraEnv` resource, and each one can adopt certain types of hosts. For example, you might want to divide your server farm between a host that has greater RAM capacity.
<1> Replace `<hosted_cluster_name>` with your hosted cluster.
31
-
<2> Replace `<hosted_cluster_namespace>` with the name of your hosted cluster namespace.
32
-
<3> The `pullSecretRef` refers to the config map reference in the same namespace as the `InfraEnv`, where the pull secret is used.
33
-
<4> The `sshAuthorizedKey` represents the SSH public key that is placed in the boot image. The SSH key allows access to the worker nodes as the `core` user.
30
+
where:
31
+
32
+
<hosted_cluster_namespace>:: Specifies the name of your hosted cluster namespace.
33
+
34
+
pullSecretRef:: Specifies the config map reference in the same namespace as the `InfraEnv`, where the pull secret is used.
35
+
36
+
sshAuthorizedKey:: Specifies the SSH public key that is placed in the boot image. The SSH key allows access to the worker nodes as the `core` user.
34
37
35
38
. Create the `InfraEnv` resource by entering the following command:
0 commit comments