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
.. View the logs for a pod that is listed in the output of the previous command by using the following command:
156
157
+
157
158
[source,terminal]
158
159
----
159
-
$ oc logs <pod_name> -n <namespace> <1>
160
+
$ oc logs <pod_name> -n <namespace>
160
161
----
161
-
<1> Specify the pod name and namespace, as shown in the output of the previous
162
-
command.
162
+
* `<namespace>`: Specify the pod name and namespace, as shown in the output of an earlier command.
163
163
+
164
-
If the pod logs display, the Kubernetes API server can communicate with the
165
-
cluster machines.
164
+
If the pod logs display, the Kubernetes API server can communicate with the cluster machines.
166
165
167
166
ifndef::ibm-power[]
168
167
. For an installation with Fibre Channel Protocol (FCP), additional steps are required to enable multipathing. Do not enable multipathing during installation.
@@ -187,23 +186,22 @@ If you have enabled secure boot during the {product-title} bootstrap process, th
187
186
[source,terminal]
188
187
----
189
188
$ oc debug node/<node_name>
190
-
chroot /host
191
189
----
192
190
+
193
-
. Confirm that secure boot is enabled by running the following command:
194
-
+
191
+
.Example output
195
192
[source,terminal]
196
193
----
197
-
$ cat /sys/firmware/ipl/secure
194
+
chroot /host
198
195
----
196
+
197
+
. Confirm that secure boot is enabled by running the following command. Example output states `1` if secure boot is enabled and `0` if secure boot is not enabled.
199
198
+
200
-
.Example output
201
199
[source,terminal]
202
200
----
203
-
1 <1>
201
+
$ cat /sys/firmware/ipl/secure
204
202
----
205
-
<1> The value is `1` if secure boot is enabled and `0` if secure boot is not enabled.
206
203
endif::ibm-z,ibm-z-lpar[]
204
+
207
205
ifdef::ibm-z-lpar[]
208
206
. List the re-IPL configuration by running the following command:
You must export a common set of variables that are used with the provided Azure
23
-
Resource Manager (ARM) templates used to assist in completing a user-provided
24
-
infrastructure install on Microsoft {cp}.
22
+
You must export a common set of variables that are used with the provided Azure Resource Manager (ARM) templates used to assist in completing a user-provided infrastructure install on Microsoft {cp}.
25
23
26
24
[NOTE]
27
25
====
28
-
Specific ARM templates can also require additional exported variables, which are
29
-
detailed in their related procedures.
26
+
Specific ARM templates can also require additional exported variables, which are detailed in their related procedures.
30
27
====
31
28
32
29
.Prerequisites
@@ -35,67 +32,51 @@ detailed in their related procedures.
35
32
36
33
.Procedure
37
34
38
-
. Export common variables found in the `install-config.yaml` to be used by the
39
-
provided ARM templates:
35
+
. Export common variables found in the `install-config.yaml` to be used by the provided ARM templates:
40
36
+
41
37
[source,terminal]
42
38
----
43
39
$ export CLUSTER_NAME=<cluster_name>
44
40
----
45
-
+
46
-
where:
47
-
+
48
-
`<cluster_name>`:: The value of the `.metadata.name` attribute from the `install-config.yaml` file.
41
+
* `<cluster_name>`: The value of the `.metadata.name` attribute from the `install-config.yaml` file.
49
42
+
50
43
[source,terminal]
51
44
----
52
45
$ export AZURE_REGION=<azure_region>
53
46
----
54
-
+
55
-
where:
56
-
+
57
47
ifndef::ash[]
58
-
`<azure_region>`:: The region to deploy the cluster into, for example `centralus`. This is the value of the `.platform.azure.region` attribute from the `install-config.yaml` file.
48
+
* `<azure_region>`: The region to deploy the cluster into, for example `centralus`. This is the value of the `.platform.azure.region` attribute from the `install-config.yaml` file.
59
49
endif::ash[]
60
50
ifdef::ash[]
61
-
`<azure_region>`:: The region to deploy the cluster into. This is the value of the `.platform.azure.region` attribute from the `install-config.yaml` file.
51
+
* `<azure_region>`: The region to deploy the cluster into. This is the value of the `.platform.azure.region` attribute from the `install-config.yaml` file.
62
52
endif::ash[]
63
53
+
64
54
[source,terminal]
65
55
----
66
56
$ export SSH_KEY=<ssh_key>
67
57
----
68
-
+
69
-
where:
70
-
+
71
-
`<ssh_key>`:: The SSH RSA public key file as a string. You must enclose the SSH key in quotes since it contains spaces. This is the value of the `.sshKey` attribute from the `install-config.yaml` file.
58
+
* `<ssh_key>`: The SSH RSA public key file as a string. You must enclose the SSH key in quotes since it contains spaces. This is the value of the `.sshKey` attribute from the `install-config.yaml` file.
72
59
+
73
60
[source,terminal]
74
61
----
75
62
$ export BASE_DOMAIN=<base_domain>
76
63
----
77
-
+
78
-
where:
79
-
+
80
64
ifndef::ash[]
81
-
`<base_domain>`:: The base domain to deploy the cluster to. The base domain corresponds to the public DNS zone that you created for your cluster. This is the value of the `.baseDomain` attribute from the `install-config.yaml` file.
65
+
* `<base_domain>`: The base domain to deploy the cluster to. The base domain corresponds to the public DNS zone that you created for your cluster. This is the value of the `.baseDomain` attribute from the `install-config.yaml` file.
82
66
endif::ash[]
83
67
ifdef::ash[]
84
-
`<base_domain>`:: The base domain to deploy the cluster to. The base domain corresponds to the DNS zone that you created for your cluster. This is the value of the `.baseDomain` attribute from the `install-config.yaml` file.
68
+
* `<base_domain>`: The base domain to deploy the cluster to. The base domain corresponds to the DNS zone that you created for your cluster. This is the value of the `.baseDomain` attribute from the `install-config.yaml` file.
`<base_domain_resource_group>`:: The resource group where the public DNS zone exists. This is the value of the `.platform.azure.baseDomainResourceGroupName` attribute from the `install-config.yaml` file.
76
+
* `<base_domain_resource_group>`: The resource group where the public DNS zone exists. This is the value of the `.platform.azure.baseDomainResourceGroupName` attribute from the `install-config.yaml` file.
96
77
endif::ash[]
97
78
ifdef::ash[]
98
-
`<base_domain_resource_group>`:: The resource group where the DNS zone exists. This is the value of the `.platform.azure.baseDomainResourceGroupName` attribute from the `install-config.yaml` file.
79
+
* `<base_domain_resource_group>`: The resource group where the DNS zone exists. This is the value of the `.platform.azure.baseDomainResourceGroupName` attribute from the `install-config.yaml` file.
Copy file name to clipboardExpand all lines: modules/installation-user-infra-machines-advanced-customizing-live-network-config.adoc
+10-9Lines changed: 10 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,30 +20,30 @@ When creating a connection profile, you must use a `.nmconnection` filename exte
20
20
21
21
. Create a connection profile for a bonded interface. For example, create the `bond0.nmconnection` file in your local directory with the following content:
22
22
+
23
-
[source,ini]
23
+
[source,terminal,subs="quotes,verbatim"]
24
24
----
25
-
[connection]
25
+
/[connection]
26
26
id=bond0
27
27
type=bond
28
28
interface-name=bond0
29
29
multi-connect=1
30
30
31
-
[bond]
31
+
/[bond]
32
32
miimon=100
33
33
mode=active-backup
34
34
35
-
[ipv4]
35
+
/[ipv4]
36
36
method=auto
37
37
38
-
[ipv6]
38
+
/[ipv6]
39
39
method=auto
40
40
----
41
41
42
42
. Create a connection profile for a secondary interface to add to the bond. For example, create the `bond0-proxy-em1.nmconnection` file in your local directory with the following content:
43
43
+
44
-
[source,ini]
44
+
[source,terminal,subs="quotes,verbatim"]
45
45
----
46
-
[connection]
46
+
/[connection]
47
47
id=em1
48
48
type=ethernet
49
49
interface-name=em1
@@ -54,9 +54,9 @@ slave-type=bond
54
54
55
55
. Create a connection profile for a secondary interface to add to the bond. For example, create the `bond0-proxy-em2.nmconnection` file in your local directory with the following content:
Copy file name to clipboardExpand all lines: modules/installation-user-infra-machines-advanced-enabling-serial-console.adoc
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,23 +20,26 @@ By default, the {op-system-first} serial console is disabled and all output is w
20
20
21
21
. Run the `coreos-installer` command to install the system, adding the `--console` option once to specify the graphical console, and a second time to specify the serial console:
<1> The desired secondary console. In this case, the graphical console. Omitting this option will disable the graphical console.
42
45
<2> The desired primary console. In this case the serial console. The `options` field defines the baud rate and other settings. A common value for this field is `115200n8`. If no options are provided, the default kernel value of `9600n8` is used. For more information on the format of this option, see link:https://www.kernel.org/doc/html/latest/admin-guide/serial-console.html[Linux kernel serial console] documentation.
0 commit comments