forked from pivotal-cf/docs-pks
-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html.md.erb
223 lines (169 loc) · 7.43 KB
/
index.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
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
---
title: Pivotal Container Service (PKS)
owner: PKS
---
<strong><%= modified_date %></strong>
Pivotal Container Service (PKS) enables operators to provision, operate, and manage enterprise-grade Kubernetes clusters using BOSH and Pivotal Ops Manager.
## <a id='overview'></a>Overview
PKS uses the [On-Demand Broker](https://docs.pivotal.io/svc-sdk/odb/index.html) to deploy [Cloud Foundry Container Runtime](https://docs-kubo.cfapps.io/), a BOSH release that offers a uniform way to instantiate, deploy, and manage highly available Kubernetes clusters on a cloud platform using BOSH.
After operators install the PKS tile on the Ops Manager Installation Dashboard, developers can provision Kubernetes clusters using the PKS Command Line Interface (PKS CLI), and run container-based workloads on the clusters with the Kubernetes CLI, [kubectl](installing-kubectl-cli.html).
PKS is available as part of [Pivotal Cloud Foundry](https://docs.pivotal.io) or as a stand-alone product.
##<a id='pks-kubernetes'></a> What PKS Adds to Kubernetes
The following table details the features that PKS adds to the Kubernetes platform.
<table>
<tr>
<th>Feature</th>
<th>Included in K8s</th>
<th>Included in PKS</th>
</tr>
<tr>
<td>Single tenant ingress</td>
<td align="center">✓</td>
<td align="center">✓</td>
</tr>
<tr>
<td>Secure multi-tenant ingress</td>
<td></td>
<td align="center">✓</td>
</tr>
<tr>
<td>Stateful sets of pods</td>
<td align="center">✓</td>
<td align="center">✓</td>
</tr>
<tr>
<td>Multi-container pods</td>
<td align="center">✓</td>
<td align="center">✓</td>
</tr>
<tr>
<td>Rolling upgrades to pods</td>
<td align="center">✓</td>
<td align="center">✓</td>
</tr>
<tr>
<td>Rolling upgrades to cluster infrastructure</td>
<td></td>
<td align="center">✓</td>
</tr>
<tr>
<td>Pod scaling and high availability</td>
<td align="center">✓</td>
<td align="center">✓</td>
</tr>
<tr>
<td>Cluster provisioning and scaling</td>
<td></td>
<td align="center">✓</td>
</tr>
<tr>
<td>Monitoring and recovery of cluster VMs and processes</td>
<td></td>
<td align="center">✓</td>
</tr>
<tr>
<td>Persistent disks</td>
<td align="center">✓</td>
<td align="center">✓</td>
</tr>
<tr>
<td>Secure container registry</td>
<td></td>
<td align="center">✓</td>
</tr>
<tr>
<td>Embedded, hardened operating system</td>
<td></td>
<td align="center">✓</td>
</tr>
</table>
## <a id='features'></a>Features
PKS has the following features:
* **Kubernetes compatibility**: Constant compatibility with current stable release of Kubernetes
* **Production-ready**: Highly available from applications to infrastructure, with no single points of failure
* **BOSH advantages**: Built-in health checks, scaling, auto-healing and rolling upgrades
* **Fully automated operations**: Fully automated deploy, scale, patch, and upgrade experience
* **Multi-cloud**: Consistent operational experience across multiple clouds
* **GCP APIs access**: The Google Cloud Platform (GCP) Service Broker gives applications access to the Google Cloud APIs, and Google Container Engine (GKE) consistency enables the transfer of workloads from or to GCP
On vSphere, PKS supports deploying and running Kubernetes clusters in air-gapped environments.
##<a id='components'></a> PKS Components
The PKS control plane contains the following components:
* An [On-Demand Broker](https://docs.pivotal.io/svc-sdk/odb/) that deploys [Cloud Foundry Container Runtime](https://docs-kubo.cfapps.io) (CFCR), an open-source project that provides a solution for deploying and managing [Kubernetes](https://kubernetes.io/docs/home/) clusters using [BOSH](https://bosh.io/docs).
* A Service Adapter
* The PKS API
For more information about the PKS control plane, see [PKS Cluster Management](control-plane.html).
For a detailed list of components and supported versions by a particular PKS release, see the [PKS Release Notes](release-notes.html).
## <a id='concepts'></a>PKS Concepts
For conceptual information about PKS, see [PKS Concepts](concepts.html).
##<a id='prerequisites'></a> PKS Prerequisites
For information about the resource requirements for installing PKS, see the topic that corresponds to your cloud provider:
* [vSphere Prerequisites and Resource Requirements](vsphere-requirements.html)
* [vSphere with NSX-T Version Requirements](vsphere-nsxt-requirements.html) and [Hardware Requirements for PKS on vSphere with NSX-T](vsphere-nsxt-rpd-mpd.html)
* [GCP Prerequisites and Resource Requirements](gcp-requirements.html)
* [AWS Prerequisites and Resource Requirements](aws-requirements.html)
* [Azure Prerequisites and Resource Requirements](azure-requirements.html)
##<a id='preparing'></a> Preparing to Install PKS
To install PKS, you must deploy one of the following versions of Ops Manager:
* Ops Manager v2.3.1 or later
* Ops Manager v2.4.x
You use Ops Manager to install and configure PKS.
If you are installing PKS to vSphere, you can also configure integration with NSX-T and Harbor.
Consult the following table for compatibility information:
<table>
<tr>
<th>IaaS</th>
<th>Ops Manager v2.3.1+ or v2.4.x</th>
<th>NSX-T</th>
<th>Harbor</th>
</tr>
<tr>
<td>vSphere</td>
<td>Required</td>
<td>Available</td>
<td>Available</td>
</tr>
<tr>
<td>GCP</td>
<td>Required</td>
<td>Not Available</td>
<td>Available</td>
</tr>
<tr>
<td>AWS</td>
<td>Required</td>
<td>Not Available</td>
<td>Available</td>
</tr>
<tr>
<td>Azure</td>
<td>Required</td>
<td>Not Available</td>
<td>Not Available</td>
</tr>
</table>
For more information about compatibility and component versions, see the [PKS Release Notes](release-notes.html).
For information about preparing your environment before installing PKS, see the topic that corresponds to your cloud provider:
* [vSphere](vsphere-index.html)
* [vSphere with NSX-T Integration](vsphere-nsxt-index.html)
* [GCP](gcp-index.html)
* [AWS](aws-index.html)
* [Azure](azure-index.html)
## <a id='installing'></a>Installing PKS
For information about installing PKS, see _Installing PKS_ for your IaaS:
* [vSphere](installing-pks-vsphere.html)
* [vSphere with NSX-T Integration](installing-nsx-t.html)
* [Google Cloud Platform (GCP)](installing-pks-gcp.html)
* [Amazon Web Services (AWS)](installing-pks-aws.html)
* [Microsoft Azure (Azure)](installing-pks-azure.html)
## <a id='upgrading'></a>Upgrading PKS
For information about upgrading the PKS tile and PKS-deployed Kubernetes clusters, see [Upgrading PKS Overview](upgrading.html).
## <a id='managing'></a>Managing PKS
For information about configuring authentication, creating users, and managing your PKS deployment, see [Managing PKS](managing.html).
## <a id='using'></a>Using PKS
For information about using the PKS CLI to create and manage Kubernetes clusters, see [Using PKS](using.html).
## <a id='backup'></a>Backing Up and Restoring PKS
For information about using BOSH Backup and Restore (BBR) to back up and restore PKS, see [Backing Up and Restoring PKS](backup-and-restore.html).
## <a id='security'></a>PKS Security
For information about security in PKS, see [PKS Security](security.html).
## <a id='troubleshooting'></a>Diagnosing and Troubleshooting PKS
For information about diagnosing and troubleshooting issues installing or using PKS, see [Diagnosing and Troubleshooting PKS](troubleshoot.html).