forked from pivotal-cf/docs-pks
-
Notifications
You must be signed in to change notification settings - Fork 0
/
installing-pks-gcp.html.md.erb
184 lines (119 loc) · 7.45 KB
/
installing-pks-gcp.html.md.erb
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
---
title: Installing Enterprise PKS on GCP
owner: PKS
iaas: GCP
---
<strong><%= modified_date %></strong>
This topic describes how to install and configure <%= vars.product_full %> on Google Cloud Platform (GCP).
##<a id='prerequisites'></a>Prerequisites
Before performing the procedures in this topic, you must have deployed and configured Ops Manager.
For more information, see [GCP Prerequisites and Resource Requirements](gcp-requirements.html).
<%= partial 'prerequisites' %>
##<a id='install'></a> Step 1: Install <%= vars.product_short %>
<%= partial 'install-pks' %>
##<a id='configure'></a> Step 2: Configure <%= vars.product_short %>
Click the orange **<%= vars.product_tile %>** tile to start the configuration process.
<p class="note warning"><strong>Warning:</strong> When you configure the <%= vars.product_tile %> tile
do not use spaces in any field entries. This includes spaces between characters as well as
leading and trailing spaces. If you use a space in any field entry, the deployment of <%= vars.product_short %> fails.</p>
###<a id='azs-networks'></a> Assign AZs and Networks
<%= partial 'azs-networks' %>
###<a id='pks-api'></a> PKS API
<%= partial 'pks-api' %>
###<a id='plans'></a> Plans
<%= partial 'plans' %>
###<a id='cloud-provider'></a> Kubernetes Cloud Provider
To configure your Kubernetes cloud provider settings, follow the procedures below:
1. Click **Kubernetes Cloud Provider**.
1. Under **Choose your IaaS**, select **GCP**.
1. Ensure the values in the following procedure match those in the **Google Config** section of the Ops Manager tile as follows:
<img src="images/cloud-gcp.png" alt="GCP pane configuration" width="325">
1. Enter your **GCP Project ID**, which is the name of the deployment in your Ops Manager environment.
To find the project ID, go to **BOSH Director for GCP** > **Google Config** > **Project ID**.
1. Enter your **VPC Network**, which is the VPC network name for your Ops Manager environment.
1. Enter your **GCP Master Service Account ID**.
This is the email address associated with the master node service account.
+ **If you are installing <%= vars.product_short %> manually:** You configured the
master node service account in [Create the Master Node Service Account](gcp-service-accounts.html#create-master)
in _Creating Service Accounts in GCP for <%= vars.product_short %>_.
+ **If you are installing <%= vars.product_short %> with Terraform:** Retrieve the
master node service account ID by running `terraform output` and locating the value for
`pks_master_node_service_account_email`.
1. Enter your **GCP Worker Service Account ID**.
This is the email address associated with the worker node service account.
+ **If you are installing <%= vars.product_short %> manually:** You configured the worker
node service account in [Create the Worker Node Service Account](gcp-service-accounts.html#create-worker)
in _Creating Service Accounts in GCP for <%= vars.product_short %>_.
+ **If you are installing <%= vars.product_short %> with Terraform:** Retrieve the
worker node service account ID by running `terraform output` and locating the value for
`pks_worker_node_service_account_email`.
1. Click **Save**.
###<a id='syslog'></a> (Optional) Logging
<%= partial 'logging' %>
###<a id='networking'></a> Networking
To configure networking, do the following:
1. Click **Networking**.
1. Under **Container Networking Interface**, select **Flannel**.
<img src="images/networking-flannel.png" alt="Networking pane configuration" width="425">
1. (Optional) Enter values for **Kubernetes Pod Network CIDR Range** and **Kubernetes Service Network CIDR Range**.
* Ensure that the CIDR ranges do not overlap and have sufficient space for your deployed services.
* Ensure that the CIDR range for the **Kubernetes Pod Network CIDR Range** is large enough to accommodate the expected maximum number of pods.
1. (Optional) If you do not use a NAT instance, select **Allow outbound internet access from Kubernetes cluster vms (IaaS-dependent)**. Enabling this functionality assigns external IP addresses to VMs in clusters.
1. Click **Save**.
###<a id='uaa'></a> UAA
<%= partial 'uaa' %>
###<a id='monitoring'></a> (Optional) Monitoring
<%= partial 'monitoring' %>
###<a id='telemetry'></a> CEIP and Telemetry
<%= partial 'usage-data' %>
###<a id='errands'></a> Errands
<%= partial 'errands' %>
###<a id='resource-config'></a> Resource Config
To modify the resource usage of <%= vars.product_short %> and specify your PKS API load balancer,
follow the steps below:
1. Select **Resource Config**.
1. In the **Load Balancers** column, enter the name of your PKS API load balancer, prefixed with `tcp:`.
For example:
```
tcp:PKS-API-LB
```
Where `PKS-API-LB` is the name of your PKS API load balancer.<br><br>
You can find the name of your PKS API load balancer by doing one of the following:
+ **If you are installing <%= vars.product_short %> manually:** The name of your PKS API load
balancer is the name you configured in the [Create a Load Balancer](gcp-api-load-balancer.html#create-lb)
section of _Creating a GCP Load Balancer for the PKS API_.
+ **If you are installing <%= vars.product_short %> using Terraform:** The name of your PKS API
load balancer is the value of `pks_lb_backend_name` from `terraform output`.
<%= partial 'lb-resource-config' %>
1. (Optional) Edit other resources used by the **Pivotal Container Service** job.
The **Pivotal Container Service** job requires a VM with the following minimum
resources:
<table>
<tr>
<th>CPU</th>
<th>Memory</th>
<th>Disk</th>
</tr>
<tr>
<td>2</td>
<td>8 GB</td>
<td>29 GB</td>
</tr>
</table>
<p class="note"><strong>Note</strong>: The automatic <b>VM Type</b> value matches the minimum recommended size for the <b>Pivotal Container Service</b> job. If you experience timeouts or slowness when interacting with the PKS API, select a <strong>VM Type</strong> with greater CPU and memory resources.</p>
## <a id='apply-changes'></a> Step 3: Apply Changes
<%= partial 'apply-changes' %>
##<a id='retrieve-pks-api'></a> Step 4: Retrieve the PKS API Endpoint
<%= partial 'share-endpoint' %>
## <a id='loadbalancer-pks-api'></a> Step 5: Configure External Load Balancer
If you are installing <%= vars.product_short %> manually, follow the procedure in the [Create a Network Tag for the Firewall Rule](gcp-api-load-balancer.html#tag) section of _Creating a GCP Load Balancer for the PKS API_.
## <a id='clis'></a> Step 6: Install the PKS and Kubernetes CLIs
<%= partial 'install-cli' %>
## <a id='auth'></a> Step 7: Configure Authentication for <%= vars.product_short %>
Follow the procedures in [Setting Up <%= vars.product_short %> Admin Users on GCP](gcp-configure-pks-users.html).
##<a id='next-steps'></a> Next Steps
After installing <%= vars.product_short %> on GCP, you may want to do one or more of the following:
* Create a load balancer for your <%= vars.product_short %> clusters. For more information, see [Creating and Configuring a GCP Load Balancer for <%= vars.product_short %> Clusters](gcp-cluster-load-balancer.html).
* Create your first <%= vars.product_short %> cluster. For more information, see [Creating Clusters](create-cluster.html).