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
= Creating the Kubernetes manifest and Ignition config files
@@ -86,6 +112,21 @@ The installation configuration file transforms into the Kubernetes manifests. Th
86
112
The Ignition config files that the {product-title} installation program generates contain certificates that expire after 24 hours, which are then renewed at that time. If the cluster is shut down before renewing the certificates and the cluster is later restarted after the 24 hours have elapsed, the cluster automatically recovers the expired certificates. The exception is that you must manually approve the pending `node-bootstrapper` certificate signing requests (CSRs) to recover kubelet certificates. See the documentation for _Recovering from expired control plane certificates_ for more information.
87
113
====
88
114
115
+
ifdef::ibm-z[]
116
+
[NOTE]
117
+
====
118
+
The installation program that generates the manifest and Ignition files is architecture specific and can be obtained from the
119
+
link:https://mirror.openshift.com/pub/openshift-v4/s390x/clients/ocp/latest/[client image mirror]. The Linux version of the installation program runs on s390x only. This installer program is also available as a Mac OS version.
120
+
====
121
+
endif::ibm-z[]
122
+
ifdef::ibm-power[]
123
+
[NOTE]
124
+
====
125
+
The installation program that generates the manifest and Ignition files is architecture specific and can be obtained from the
126
+
link:https://mirror.openshift.com/pub/openshift-v4/ppc64le/clients/ocp/latest/[client image mirror]. The Linux version of the installation program runs on ppc64le only. This installer program is also available as a Mac OS version.
127
+
====
128
+
endif::ibm-power[]
129
+
89
130
.Prerequisites
90
131
91
132
* You obtained the {product-title} installation program.
@@ -157,13 +198,13 @@ to initialize them.
157
198
+
158
199
* You can preserve the machine set files to create compute machines by using the machine API, but you must update references to them to match your environment.
. Check that the `mastersSchedulable` parameter in the `<installation_directory>/manifests/cluster-scheduler-02-config.yml` Kubernetes manifest file is set to `false`. This setting prevents pods from being scheduled on the control plane machines:
0 commit comments