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
* xref:../../installing/installing_gcp/installation-config-parameters-gcp.adoc#installation-config-parameters-gcp[Installation configuration parameters for GCP]
67
68
* xref:../../machine_management/creating_machinesets/creating-machineset-gcp.adoc#machineset-enabling-customer-managed-encryption_creating-machineset-gcp[Enabling customer-managed encryption keys for a compute machine set]
* xref:../../installing/installing_gcp/installation-config-parameters-gcp.adoc#installation-config-parameters-gcp[Installation configuration parameters for GCP]
69
70
* xref:../../machine_management/creating_machinesets/creating-machineset-gcp.adoc#machineset-enabling-customer-managed-encryption_creating-machineset-gcp[Enabling customer-managed encryption keys for a compute machine set]
* xref:../../installing/installing_gcp/installation-config-parameters-gcp.adoc#installation-config-parameters-gcp[Installation configuration parameters for GCP]
66
67
* xref:../../machine_management/creating_machinesets/creating-machineset-gcp.adoc#machineset-enabling-customer-managed-encryption_creating-machineset-gcp[Enabling customer-managed encryption keys for a compute machine set]
= Sample customized install-config.yaml file for {gcp-full}
12
+
13
+
[role="_abstract"]
14
+
To specify more details about your {product-title} cluster's platform or modify the values of the required parameters, you can customize the `install-config.yaml` file.
15
+
16
+
[IMPORTANT]
17
+
====
18
+
This sample YAML file is provided for reference only. You must obtain your `install-config.yaml` file by using the installation program and modify it.
19
+
====
20
+
21
+
[source,yaml]
22
+
----
23
+
apiVersion: v1
24
+
baseDomain: example.com
25
+
pullSecret: '{"auths": ...}'
26
+
controlPlane:
27
+
name: master
28
+
replicas: 3
29
+
platform:
30
+
gcp:
31
+
type: n2-standard-4
32
+
compute:
33
+
- name: worker
34
+
replicas: 3
35
+
platform:
36
+
gcp:
37
+
type: n2-standard-4
38
+
metadata:
39
+
name: test-cluster
40
+
networking:
41
+
clusterNetwork:
42
+
- cidr: 10.128.0.0/14
43
+
hostPrefix: 23
44
+
platform:
45
+
gcp:
46
+
projectID: sample-project
47
+
region: us-east1
48
+
----
49
+
where:
50
+
51
+
`controlPlane`:: Specifies parameters that apply to control plane machines.
52
+
`compute`:: Specifies parameters that apply to compute machines.
53
+
`networking`:: Specifies parameters that apply to the cluster networking configuration. If you do not provide networking values, the installation program provides default values.
54
+
`platform`:: Specifies parameters that apply to the infrastructure platform that hosts the cluster.
You must create a directory. Some installation assets, such as bootstrap X.509 certificates have short expiration intervals, so you must not reuse an installation directory. If you want to reuse individual files from another cluster installation, you can copy them into your directory. However, the file names for the installation assets might change between releases. Use caution when copying installation files from an earlier {product-title} version.
128
128
====
129
129
130
+
ifdef::gcp-private[]
131
+
. Edit the `install-config.yaml` file to set the `publish: Internal` parameter.
132
+
. Edit the `install-config.yaml` file to set the parameters necessary for installation into an existing VPC.
133
+
.. Define the network and subnets for the VPC to install the cluster in under the parent `platform.gcp` field:
134
+
+
135
+
[source,yaml]
136
+
----
137
+
platform:
138
+
gcp:
139
+
network: <existing_vpc>
140
+
controlPlaneSubnet: <control_plane_subnet>
141
+
computeSubnet: <compute_subnet>
142
+
----
143
+
+
144
+
For the `platform.gcp.network` parameter, specify the name for the existing Google VPC. For the `platform.gcp.controlPlaneSubnet` and `platform.gcp.computeSubnet` parameters, specify the existing subnets to deploy the control plane machines and compute machines, respectively.
145
+
endif::gcp-private[]
146
+
ifdef::gcp-shared[]
147
+
. Edit the `install-config.yaml` file to set the parameters necessary for installation into a shared VPC.
148
+
.. Define the network, subnets, and project names for the shared VPC:
. Modify the `install-config.yaml` file. You can find more information about the available parameters in the "Installation configuration parameters" section.
461
463
endif::restricted,nutanix,aws-outposts[]
464
+
ifdef::gcp-vpc[]
465
+
.. Define the network and subnets for the VPC to install the cluster in under the parent `platform.gcp` field:
466
+
+
467
+
[source,yaml]
468
+
----
469
+
platform:
470
+
gcp:
471
+
network: <existing_vpc>
472
+
controlPlaneSubnet: <control_plane_subnet>
473
+
computeSubnet: <compute_subnet>
474
+
----
475
+
+
476
+
For `platform.gcp.network`, specify the name for the existing Google VPC. For `platform.gcp.controlPlaneSubnet` and `platform.gcp.computeSubnet`, specify the existing subnets to deploy the control plane machines and compute machines, respectively.
477
+
endif::gcp-vpc[]
462
478
ifdef::three-node-cluster[]
463
479
+
464
480
[NOTE]
@@ -581,19 +597,21 @@ where:
581
597
`<control_plane_subnet>`:: Replace `<control_plane_subnet>` with the existing subnet name to deploy the control plane machines.
582
598
`<compute_subnet>:: Replace `<compute_subnet>` with the existing subnet name to deploy compute machines.
583
599
endif::azure+restricted[]
584
-
ifdef::gcp+restricted[]
600
+
ifdef::gcp-restricted[]
585
601
+
586
602
.. Define the network and subnets for the VPC to install the cluster in under the parent `platform.gcp` field:
587
603
+
588
604
[source,yaml]
589
605
----
590
-
network: <existing_vpc>
591
-
controlPlaneSubnet: <control_plane_subnet>
592
-
computeSubnet: <compute_subnet>
606
+
platform:
607
+
gcp:
608
+
network: <existing_vpc>
609
+
controlPlaneSubnet: <control_plane_subnet>
610
+
computeSubnet: <compute_subnet>
593
611
----
594
612
+
595
613
For `platform.gcp.network`, specify the name for the existing Google VPC. For `platform.gcp.controlPlaneSubnet` and `platform.gcp.computeSubnet`, specify the existing subnets to deploy the control plane machines and compute machines, respectively.
596
-
endif::gcp+restricted[]
614
+
endif::gcp-restricted[]
597
615
ifdef::ibm-power-vs+restricted[]
598
616
+
599
617
.. Define the network for the VPC to install the cluster in under the parent `platform.powervs` field:
@@ -672,7 +690,7 @@ Only one VPE can be specified per service.
672
690
endif::ibm-cloud[]
673
691
ifdef::restricted[]
674
692
+
675
-
.. Set the publishing strategy to `Internal`:
693
+
.. Optionally, set the publishing strategy to `Internal`:
Copy file name to clipboardExpand all lines: modules/private-clusters-about-gcp.adoc
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,8 @@
6
6
[id="private-clusters-about-gcp_{context}"]
7
7
= Private clusters in {gcp-short}
8
8
9
-
To create a private cluster on {gcp-first}, you must provide an existing private VPC and subnets to host the cluster. The installation program must also be able to resolve the DNS records that the cluster requires. The installation program configures the Ingress Operator and API server for only internal traffic.
9
+
[role="_abstract"]
10
+
To create a private cluster on {gcp-first}, you must provide an existing VPC network and subnets to host the cluster, and you must specify `publish: Internal` in your `install-config.yaml` file. The installation program must also be able to resolve the DNS records that the cluster requires. The installation program configures the Ingress Operator and API server for only internal traffic.
10
11
11
12
The cluster still requires access to internet to access the {gcp-short} APIs.
0 commit comments