forked from pivotal-cf/docs-pks
-
Notifications
You must be signed in to change notification settings - Fork 0
/
installing-pks-aws.html.md.erb
135 lines (77 loc) · 4.94 KB
/
installing-pks-aws.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
---
title: Installing PKS on AWS
owner: PKS
iaas: AWS
---
<strong><%= modified_date %></strong>
This topic describes how to install and configure Pivotal Container Service (PKS) on Amazon Web Services (AWS).
##<a id='prerequisites'></a>Prerequisites
Before performing the procedures in this topic, you must have deployed and configured Ops Manager.
For more information, see [AWS Prerequisites and Resource Requirements](aws-requirements.html).
<%= partial 'prerequisites' %>
##<a id='install'></a> Step 1: Install PKS
<%= partial 'install-pks' %>
##<a id='configure'></a> Step 2: Configure PKS
Click the orange **Pivotal Container Service** tile to start the configuration process.
![Pivotal Container Service tile on the Ops Manager installation dashboard](images/pks-tile-orange.png)
<p class="note warning"><strong>WARNING</strong>: When you configure the PKS 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 PKS 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 **AWS**.
<img src="images/cloud-aws.png" alt="AWS pane configuration" width="325">
1. Enter your **AWS Master Instance Profile IAM**. This is the instance profile name associated with the master node. To retrieve the instance profile name, run `terraform output` and locate the value for the field `pks_master_iam_instance_profile_name`.
1. Enter your **AWS Worker Instance Profile IAM**. This is the instance profile name associated with the worker node. To retrieve the instance profile name, run `terraform output` and locate the value for the field `pks_worker_iam_instance_profile_name`.
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='usage'></a> Usage Data
<%= partial 'usage-data' %>
###<a id='errands'></a> Errands
<%= partial 'errands' %>
###<a id='resource-config'></a> Resource Config
To modify the resource usage of PKS and specify your PKS API load balancer, follow the steps below:
1. Select **Resource Config**.
1. In the **Load Balancers** column, enter `pks-api`. Terraform created this load
balancer when you ran `terraform apply plan` in [Preparing to Deploy PCF on AWS
Using Terraform](http://docs.pivotal.io/pcf/om/2-4/aws/prepare-env-terraform.html).
<%= partial 'lb-resource-config' %>
1. (Optional) Edit other resources used by the **Pivotal Container Service** job.
![Resource pane configuration](images/aws-resources.png)
<p class="note"><strong>Note</strong>: If you experience timeouts or slowness when interacting with the PKS API, select a <strong>VM Type</strong> with greater CPU and memory resources for the <strong>Pivotal Container Service</strong> job.</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='clis'></a> Step 5: Install the PKS and Kubernetes CLIs
<%= partial 'install-cli' %>
## <a id='api'></a> Step 6: Configure PKS API Access
Follow the procedures in [Configuring PKS API Access](configure-api.html).
## <a name='auth'></a> Step 7: Configure Authentication for PKS
<%= partial 'configure-auth' %>
##<a id='next-steps'></a> Next Steps
After installing PKS on AWS, you may want to do one or more of the following:
* Create a load balancer for your PKS clusters. For more information, see [Creating and Configuring an AWS Load Balancer for PKS Clusters](aws-cluster-load-balancer.html).
* Create your first PKS cluster. For more information, see [Creating Clusters](create-cluster.html).