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
Copy file name to clipboardExpand all lines: modules/installation-configuration-parameters.adoc
+24Lines changed: 24 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1383,6 +1383,22 @@ Additional GCP configuration parameters are described in the following table:
1383
1383
|====
1384
1384
|Parameter|Description|Values
1385
1385
1386
+
|`controlPlane.platform.gcp.osImage.project`
1387
+
|Optional. By default, the installation program downloads and installs the {op-system-first} image that is used to boot control plane machines. You can override the default behavior by specifying the location of a custom {op-system} image that the installation program is to use for control plane machines only.
1388
+
|String. The name of GCP project where the image is located.
1389
+
1390
+
|`controlPlane.platform.gcp.osImage.name`
1391
+
|The name of the custom {op-system} image that the installation program is to use to boot control plane machines. If you use `controlPlane.platform.gcp.osImage.project`, this field is required.
1392
+
|String. The name of the {op-system} image.
1393
+
1394
+
|`compute.platform.gcp.osImage.project`
1395
+
|Optional. By default, the installation program downloads and installs the {op-system} image that is used to boot compute machines. You can override the default behavior by specifying the location of a custom {op-system} image that the installation program is to use for compute machines only.
1396
+
|String. The name of GCP project where the image is located.
1397
+
1398
+
|`compute.platform.gcp.osImage.name`
1399
+
|The name of the custom {op-system} image that the installation program is to use to boot compute machines. If you use `compute.platform.gcp.osImage.project`, this field is required.
1400
+
|String. The name of the {op-system} image.
1401
+
1386
1402
|`platform.gcp.network`
1387
1403
|The name of the existing Virtual Private Cloud (VPC) where you want to deploy your cluster. If you want to deploy your cluster into a shared VPC, you must set `platform.gcp.networkProjectID` with the name of the GCP project that contains the shared VPC.
|Optional. By default, the installation program downloads and installs the {op-system} image that is used to boot control plane and compute machines. You can override the default behavior by specifying the location of a custom {op-system} image that the installation program is to use for both types of machines.
1449
+
|String. The name of GCP project where the image is located.
|The name of the custom {op-system} image that the installation program is to use to boot control plane and compute machines. If you use `platform.gcp.defaultMachinePlatform.osImage.project`, this field is required.
1453
+
|String. The name of the RHCOS image.
1454
+
1431
1455
|`platform.gcp.defaultMachinePlatform.tags`
1432
1456
|Optional. Additional network tags to add to the control plane and compute machines.
@@ -191,55 +200,56 @@ If you disable simultaneous multithreading, ensure that your capacity planning a
191
200
====
192
201
<5> Optional: The custom encryption key section to encrypt both virtual machines and persistent volumes. Your default compute service account must have the permissions granted to use your KMS key and have the correct IAM role assigned. The default service account name follows the `service-<project_number>@compute-system.iam.gserviceaccount.com` pattern. For more information about granting the correct permissions for your service account, see "Machine management" -> "Creating compute machine sets" -> "Creating a compute machine set on GCP".
193
202
<6> Optional: A set of network tags to apply to the control plane or compute machine sets. The `platform.gcp.defaultMachinePlatform.tags` parameter will apply to both control plane and compute machines. If the `compute.platform.gcp.tags` or `controlPlane.platform.gcp.tags` parameters are set, they override the `platform.gcp.defaultMachinePlatform.tags` parameter.
194
-
<7> The cluster network plugin to install. The supported values are `OVNKubernetes` and `OpenShiftSDN`. The default value is `OVNKubernetes`.
203
+
<7> Optional: A custom {op-system-first} that should be used to boot control plane and compute machines. The `project` and `name` parameters under `platform.gcp.defaultMachinePlatform.osImage` apply to both control plane and compute machines. If the `project` and `name` parameters under `controlPlane.platform.gcp.osImage` or `compute.platform.gcp.osImage` are set, they override the `platform.gcp.defaultMachinePlatform.osImage` parameters.
204
+
<8> The cluster network plugin to install. The supported values are `OVNKubernetes` and `OpenShiftSDN`. The default value is `OVNKubernetes`.
195
205
ifdef::vpc,restricted[]
196
-
<8> Specify the name of an existing VPC.
197
-
<9> Specify the name of the existing subnet to deploy the control plane machines to. The subnet must belong to the VPC that you specified.
198
-
<10> Specify the name of the existing subnet to deploy the compute machines to. The subnet must belong to the VPC that you specified.
206
+
<9> Specify the name of an existing VPC.
207
+
<10> Specify the name of the existing subnet to deploy the control plane machines to. The subnet must belong to the VPC that you specified.
208
+
<11> Specify the name of the existing subnet to deploy the compute machines to. The subnet must belong to the VPC that you specified.
199
209
endif::vpc,restricted[]
200
210
ifdef::restricted[]
201
-
<11> For `<local_registry>`, specify the registry domain name, and optionally the port, that your mirror registry uses to serve content. For example, `registry.example.com` or `registry.example.com:5000`. For `<credentials>`, specify the base64-encoded user name and password for your mirror registry.
211
+
<12> For `<local_registry>`, specify the registry domain name, and optionally the port, that your mirror registry uses to serve content. For example, `registry.example.com` or `registry.example.com:5000`. For `<credentials>`, specify the base64-encoded user name and password for your mirror registry.
202
212
endif::restricted[]
203
213
ifdef::vpc[]
204
214
ifndef::openshift-origin[]
205
-
<11> Whether to enable or disable FIPS mode. By default, FIPS mode is not enabled. If FIPS mode is enabled, the {op-system-first} machines that {product-title} runs on bypass the default Kubernetes cryptography suite and use the cryptography modules that are provided with {op-system} instead.
215
+
<12> Whether to enable or disable FIPS mode. By default, FIPS mode is not enabled. If FIPS mode is enabled, the {op-system-first} machines that {product-title} runs on bypass the default Kubernetes cryptography suite and use the cryptography modules that are provided with {op-system} instead.
206
216
+
207
217
[IMPORTANT]
208
218
====
209
219
The use of FIPS Validated / Modules in Process cryptographic libraries is only supported on {product-title} deployments on the `x86_64` architecture.
210
220
====
211
-
<12> You can optionally provide the `sshKey` value that you use to access the machines in your cluster.
221
+
<13> You can optionally provide the `sshKey` value that you use to access the machines in your cluster.
212
222
endif::openshift-origin[]
213
223
ifdef::openshift-origin[]
214
-
<11> You can optionally provide the `sshKey` value that you use to access the machines in your cluster.
224
+
<12> You can optionally provide the `sshKey` value that you use to access the machines in your cluster.
215
225
endif::openshift-origin[]
216
226
endif::vpc[]
217
227
ifdef::restricted[]
218
228
ifndef::openshift-origin[]
219
-
<12> Whether to enable or disable FIPS mode. By default, FIPS mode is not enabled. If FIPS mode is enabled, the {op-system-first} machines that {product-title} runs on bypass the default Kubernetes cryptography suite and use the cryptography modules that are provided with {op-system} instead.
229
+
<13> Whether to enable or disable FIPS mode. By default, FIPS mode is not enabled. If FIPS mode is enabled, the {op-system-first} machines that {product-title} runs on bypass the default Kubernetes cryptography suite and use the cryptography modules that are provided with {op-system} instead.
220
230
+
221
231
[IMPORTANT]
222
232
====
223
233
The use of FIPS Validated / Modules in Process cryptographic libraries is only supported on {product-title} deployments on the `x86_64` architecture.
224
234
====
225
-
<13> You can optionally provide the `sshKey` value that you use to access the machines in your cluster.
235
+
<14> You can optionally provide the `sshKey` value that you use to access the machines in your cluster.
226
236
endif::openshift-origin[]
227
237
ifdef::openshift-origin[]
228
-
<12> You can optionally provide the `sshKey` value that you use to access the machines in your cluster.
238
+
<13> You can optionally provide the `sshKey` value that you use to access the machines in your cluster.
229
239
endif::openshift-origin[]
230
240
endif::restricted[]
231
241
ifndef::vpc,restricted[]
232
242
ifndef::openshift-origin[]
233
-
<8> Whether to enable or disable FIPS mode. By default, FIPS mode is not enabled. If FIPS mode is enabled, the {op-system-first} machines that {product-title} runs on bypass the default Kubernetes cryptography suite and use the cryptography modules that are provided with {op-system} instead.
243
+
<9> Whether to enable or disable FIPS mode. By default, FIPS mode is not enabled. If FIPS mode is enabled, the {op-system-first} machines that {product-title} runs on bypass the default Kubernetes cryptography suite and use the cryptography modules that are provided with {op-system} instead.
234
244
+
235
245
[IMPORTANT]
236
246
====
237
247
The use of FIPS Validated / Modules in Process cryptographic libraries is only supported on {product-title} deployments on the `x86_64` architecture.
238
248
====
239
-
<9> You can optionally provide the `sshKey` value that you use to access the machines in your cluster.
249
+
<10> You can optionally provide the `sshKey` value that you use to access the machines in your cluster.
240
250
endif::openshift-origin[]
241
251
ifdef::openshift-origin[]
242
-
<8> You can optionally provide the `sshKey` value that you use to access the machines in your cluster.
252
+
<9> You can optionally provide the `sshKey` value that you use to access the machines in your cluster.
243
253
endif::openshift-origin[]
244
254
endif::vpc,restricted[]
245
255
+
@@ -249,20 +259,20 @@ For production {product-title} clusters on which you want to perform installatio
249
259
====
250
260
ifdef::private[]
251
261
ifndef::openshift-origin[]
252
-
<13> How to publish the user-facing endpoints of your cluster. Set `publish` to `Internal` to deploy a private cluster, which cannot be accessed from the internet. The default value is `External`.
262
+
<14> How to publish the user-facing endpoints of your cluster. Set `publish` to `Internal` to deploy a private cluster, which cannot be accessed from the internet. The default value is `External`.
253
263
endif::openshift-origin[]
254
264
ifdef::openshift-origin[]
255
-
<12> How to publish the user-facing endpoints of your cluster. Set `publish` to `Internal` to deploy a private cluster, which cannot be accessed from the internet. The default value is `External`.
265
+
<13> How to publish the user-facing endpoints of your cluster. Set `publish` to `Internal` to deploy a private cluster, which cannot be accessed from the internet. The default value is `External`.
256
266
endif::openshift-origin[]
257
267
endif::private[]
258
268
ifdef::restricted[]
259
269
ifndef::openshift-origin[]
260
-
<14> Provide the contents of the certificate file that you used for your mirror registry.
261
-
<15> Provide the `imageContentSources` section from the output of the command to mirror the repository.
270
+
<15> Provide the contents of the certificate file that you used for your mirror registry.
271
+
<16> Provide the `imageContentSources` section from the output of the command to mirror the repository.
262
272
endif::openshift-origin[]
263
273
ifdef::openshift-origin[]
264
-
<13> Provide the contents of the certificate file that you used for your mirror registry.
265
-
<14> Provide the `imageContentSources` section from the output of the command to mirror the repository.
274
+
<14> Provide the contents of the certificate file that you used for your mirror registry.
275
+
<15> Provide the `imageContentSources` section from the output of the command to mirror the repository.
Copy file name to clipboardExpand all lines: modules/installation-gcp-marketplace.adoc
+25-31Lines changed: 25 additions & 31 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,45 +4,39 @@
4
4
5
5
:_content-type: PROCEDURE
6
6
[id="installation-gcp-marketplace_{context}"]
7
-
= Using a GCP Marketplace image
8
-
If you want to deploy an {product-title} cluster using a GCP Marketplace image, you must create the manifests and edit the compute machine set definitions to specify the GCP Marketplace image.
7
+
= Using the GCP Marketplace offering
9
8
10
-
.Prerequisites
11
-
12
-
* You have the {product-title} installation program and the pull secret for your cluster.
9
+
Using the GCP Marketplace offering lets you deploy an {product-title} cluster, which is billed on pay-per-use basis (hourly, per core) through GCP, while still being supported directly by Red{nbsp}Hat.
13
10
14
-
.Procedure
11
+
By default, the installation program downloads and installs the {op-system-first} image that is used to deploy compute machines. To deploy an {product-title} cluster using an {op-system} image from the GCP Marketplace, override the default behavior by modifying the `install-config.yaml` file to reference the location of GCP Marketplace offer.
15
12
16
-
. Generate the installation manifests by running the following command:
0 commit comments