forked from pivotal-cf/docs-tas-kubernetes
-
Notifications
You must be signed in to change notification settings - Fork 0
/
release-notes.html.md.erb
461 lines (378 loc) · 12.1 KB
/
release-notes.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
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
---
title: Tanzu Application Service for Kubernetes Release Notes
owner: Tanzu Application Service Release Engineering
---
This topic contains release notes for Tanzu Application Service for Kubernetes
(TAS for Kubernetes).
<%= partial 'evaluation_only' %>
<%= partial 'limitation_notes' %>
## <a id='0-4-0'></a> v0.4.0
**Release Date**: TBD, 2020
### <a id='product-snapshot'></a>Product Snapshot
<table class="nice">
<tr>
<th>Release</th>
<th width=40%>Details</th>
</tr>
<tr>
<td>Version</td>
<td>v0.4.0</td>
</tr>
<tr>
<td>Release date</td>
<td>TBD, 2020</td>
</tr>
</table>
To download VMware TAS for Kubernetes v0.4.0, see
[VMware Tanzu Application Service for Kubernetes]
(https://network.pivotal.io/products/tas-for-kubernetes)
on the _VMware Tanzu Network_.
#### <a id='installed-components'></a>Installed With 0.4.0
TAS for Kubernetes uses the following components:
<table class="nice">
<tr>
<th>Element</th>
<th width=40%>Details</th>
</tr>
<tr>
<td>cf-for-k8s</td>
<td><a href="https://github.com/cloudfoundry/cf-for-k8s/commit/9854f5b0e250fbdf11b33abd956ae5a53efe7866">Commit 9854f5b</a></td>
</tr>
<tr>
<td>Istio</td>
<td>v1.4.5</td>
</tr>
<tr>
<td>kpack</td>
<td>v0.0.9</td>
</tr>
</table>
#### <a id='additional-components'></a>Required Additional Components
TAS for Kubernetes requires the following components:
<table class="nice">
<tr>
<th>Element</th>
<th width=40%>Details</th>
</tr>
<tr>
<td>BOSH CLI</td>
<td>v6.3.1</td>
</tr>
<tr>
<td>cf CLI</td>
<td>v6.51.0</td>
</tr>
<%#
<tr>
<td>Docker CLI</td>
<td>.</td>
</tr>
<tr>
<td>Harbor Registry</td>
<td>.</td>
</tr>
<tr>
<td>kubectl, the Kubernetes CLI</td>
<td>.</td>
</tr>
#%>
<tr>
<td>kapp</td>
<td>v0.29.0 or later</td>
</tr>
<tr>
<td>kbld</td>
<td>v0.23.0 or later</td>
</tr>
<tr>
<td>ytt</td>
<td>v0.28.0 or later</td>
</tr>
</table>
<%#
#### <a id='optional-components'></a>Optional Components
TAS for Kubernetes supports the following optional components:
<table class="nice">
<tr>
<th>Element</th>
<th>Details</th>
</tr>
<tr>
<td>.</td>
<td>.</td>
</tr>
<tr>
<td>.</td>
<td>.</td>
</tr>
</table>
#%>
#### <a id='supported-platforms'></a>Supported Kubernetes Distributions
TAS for Kubernetes supports the following Kubernetes distributions:
<table class="nice">
<tr>
<th>Platform</th>
<th width=40%>Version</th>
</tr>
<tr>
<td>Tanzu Kubernetes Grid</td>
<td>v1.0, with <code>metrics-server</code></td>
</tr>
<tr>
<td>VMware Enterprise PKS</td>
<td>v1.6 or v1.7</td>
</tr>
</table>
#### <a id='supported-environments'></a>Supported Environments
TAS for Kubernetes can be deployed and managed from the following desktop OS environments:
* 64-bit Mac OS
* 64-bit Linux OS
<%#
<table class="nice">
<tr>
<th>Deployment Environment</th>
<th >Version</th>
</tr>
<tr>
<td>vSphere with Flannel</td>
<td>.</td>
</tr>
<tr>
<th>Supported IaaSs</th>
<th></th>
</tr>
<tr>
<td>.</td>
<td></td>
</tr>
</table>
#%>
### <a id='features-0-4-0'></a> Features
New features and changes in this release:
- None
### <a id='breaking-0-4-0'></a> Breaking Changes
This release has the following breaking changes:
- App registry configuration files used with TAS for Kubernetes v0.3.0 and earlier
are not compatible with TAS for Kubernetes v0.4.0 and later.
For information about the current app registry configuration file
format, see [Create the Harbor Image Registry Configuration File]
(https://docs-pcf-staging.cfapps.io/tas-kubernetes/0-n/configuring-image-registries.html#harbor-config-file)
and [Create the Configuration File for a Different Image Registry]
(https://docs-pcf-staging.cfapps.io/tas-kubernetes/0-n/configuring-image-registries.html#configure-other-registry).
### <a id='known-issues-0-4-0'></a> Known Issues
This release has the following issues:
- None
## <a id='0-3-0'></a> v0.3.0
**Release Date**: July 30, 2020
### <a id='product-snapshot'></a>Product Snapshot
<table class="nice">
<tr>
<th>Release</th>
<th width=40%>Details</th>
</tr>
<tr>
<td>Version</td>
<td>v0.3.0</td>
</tr>
<tr>
<td>Release date</td>
<td>July 30, 2020</td>
</tr>
</table>
To download VMware TAS for Kubernetes v0.3.0, see
[VMware Tanzu Application Service for Kubernetes]
(https://network.pivotal.io/products/tas-for-kubernetes#/releases/691843)
on the _VMware Tanzu Network_.
#### <a id='installed-components'></a>Installed With 0.3.0
TAS for Kubernetes uses the following components:
<table class="nice">
<tr>
<th>Element</th>
<th width=40%>Details</th>
</tr>
<tr>
<td>cf-for-k8s</td>
<td><a href="https://github.com/cloudfoundry/cf-for-k8s/commit/9854f5b0e250fbdf11b33abd956ae5a53efe7866">Commit 9854f5b</a></td>
</tr>
<tr>
<td>Istio</td>
<td>v1.4.5</td>
</tr>
<tr>
<td>kpack</td>
<td>v0.0.9</td>
</tr>
</table>
#### <a id='additional-components'></a>Required Additional Components
TAS for Kubernetes requires the following components:
<table class="nice">
<tr>
<th>Element</th>
<th width=40%>Details</th>
</tr>
<tr>
<td>BOSH CLI</td>
<td>v6.3.1</td>
</tr>
<tr>
<td>cf CLI</td>
<td>v6.51.0</td>
</tr>
<%#
<tr>
<td>Docker CLI</td>
<td>.</td>
</tr>
<tr>
<td>Harbor Registry</td>
<td>.</td>
</tr>
<tr>
<td>kubectl, the Kubernetes CLI</td>
<td>.</td>
</tr>
#%>
<tr>
<td>kapp</td>
<td>v0.29.0 or later</td>
</tr>
<tr>
<td>kbld</td>
<td>v0.23.0 or later</td>
</tr>
<tr>
<td>ytt</td>
<td>v0.28.0 or later</td>
</tr>
</table>
<%#
#### <a id='optional-components'></a>Optional Components
TAS for Kubernetes supports the following optional components:
<table class="nice">
<tr>
<th>Element</th>
<th>Details</th>
</tr>
<tr>
<td>.</td>
<td>.</td>
</tr>
<tr>
<td>.</td>
<td>.</td>
</tr>
</table>
#%>
#### <a id='supported-platforms'></a>Supported Kubernetes Distributions
TAS for Kubernetes supports the following Kubernetes distributions:
<table class="nice">
<tr>
<th>Platform</th>
<th width=40%>Version</th>
</tr>
<tr>
<td>Tanzu Kubernetes Grid</td>
<td>v1.0, with <code>metrics-server</code></td>
</tr>
<tr>
<td>VMware Enterprise PKS</td>
<td>v1.6 or v1.7</td>
</tr>
</table>
#### <a id='supported-environments'></a>Supported Environments
TAS for Kubernetes can be deployed and managed from the following desktop OS environments:
* 64-bit Mac OS
* 64-bit Linux OS
<%#
<table class="nice">
<tr>
<th>Deployment Environment</th>
<th >Version</th>
</tr>
<tr>
<td>vSphere with Flannel</td>
<td>.</td>
</tr>
<tr>
<th>Supported IaaSs</th>
<th></th>
</tr>
<tr>
<td>.</td>
<td></td>
</tr>
</table>
#%>
### <a id='features-0-3-0'></a> Features
New features and changes in this release:
- Platform operators can copy system-component images into another registry and deploy TAS for Kubernetes to use those relocated images.
- Platform operators can configure their own certificates on the TAS for Kubernetes ingress gateway for TLS termination.
- TAS for Kubernetes incorporates [Paketo cloud-native buildpacks](https://paketo.io/) for Java, NodeJS, Go, .NET Core, PHP, HTTPD, and nginx.
- Istio sidecar proxies prevent all communication between apps on the Kubernetes Pod network.
- Bump Istio to version `1.4.5`
- Bump kpack to version `0.0.9`
### <a id='known-issues-0-3-0'></a> Known Issues
This release has the following issues:
- Retrieving app and buildpack-staging logs with `cf logs` requires cf CLI v6.50.0 or later.
- App instance logs also include unfiltered logs from the Istio sidecar proxy process and can be noisy as a result.
- The `cf buildpacks` command shows an empty list of buildpacks.
- Does not support cf CLI `buildpack-administration` commands.
- App developers cannot select a buildpack for their buildpack-based apps.
- The TAS for Kubernetes ingress gateway service may interfere with traffic for other Kubernetes Services in the cluster.
- TAS for Kubernetes cannot use the AWS Elastic Container Registry as its app image registry.
- Does not support upgrading an existing TAS for Kubernetes installation to a new version.
- Does not support re-deploying TAS for Kubernetes with different credentials.
## <a id='0-2-0'></a> v0.2.0
**Release Date: May 29, 2020**
### <a id='features-0-2-0'></a> Features
New features and changes in this release:
- The `cf app` command now displays CPU and memory usage metrics for app instances.
- Component metrics for Cloud Controller are now available for Prometheus to scrape via conventional `prometheus.io` annotations.
- Load-balancer options are now configured via the `enable_load_balancer` template parameter instead of via moving template overlay files.
- Ingress routing without a Kubernetes-provisioned load balancer no longer creates the `istio-ingressgateway` Kubernetes service.
### Resolved Issues
This release has the following fixes:
- Apps can now receive ingress traffic through both HTTP and HTTPS.
- Buildpack-staging logs are now streamed during `cf push`.
- Running `cf restage` now restages the app successfully.
- Running buildpack-based apps no longer requires the `diego_docker` feature flag to be set.
### <a id='known-issues-0-2-0'></a> Known Issues
This release has the following issues:
- Retrieving app and buildpack-staging logs with `cf logs` requires cf CLI v6.50.0 or later.
- App instance logs also include unfiltered logs from the Istio sidecar proxy process and can be noisy as a result.
- The `cf buildpacks` command shows an empty list of buildpacks.
- Does not support cf CLI `buildpack-administration` commands.
- App developers cannot select a buildpack for their buildpack-based apps.
- The TAS for Kubernetes ingress gateway service may interfere with traffic for other Kubernetes Services in the cluster.
- TAS for Kubernetes cannot use the AWS Elastic Container Registry as its app image registry.
- Does not support upgrading an existing TAS for Kubernetes installation to a new version.
- Does not support re-deploying TAS for Kubernetes with different credentials.
## <a id='0-1-0'></a> v0.1.0
**Release Date: April 14, 2020**
### <a id='features-0-1-0'></a> Features
Key features in this release:
- Supports building and running apps from source files through `cf push`
using system-provided cloud-native buildpacks for Java, Go, NodeJS, and .NET Core.
- Supports running apps packaged as Docker images.
- Supports routing HTTP traffic to apps.
- Supports retrieving logs from app-instance processes.
- Supports retrieving logs from cloud-native buildpack builds.
- Supports installation to Kubernetes clusters provisioned with VMware Enterprise PKS.
- Uses the k14s toolchain (ytt, kbld, and kapp) for installation.
For more information, see the [k14s](https://k14s.io) website.
- Supports integration with VMware Harbor Registry, Google Container Registry, and DockerHub for storing app images.
### <a id='known-issues-0-1-0'></a> Known Issues
This release has the following issues:
- Apps can receive ingress traffic only through HTTP and not HTTPS.
- Retrieving app and buildpack-staging logs with `cf logs` requires cf CLI v6.50.0 or later.
- Buildpack-staging logs are not streamed during `cf push`.
- App instance logs also include unfiltered logs from the Istio sidecar proxy process and can be noisy as a result.
- Running `cf restage` fails to re-stage the app.
- The `cf buildpacks` command shows an empty list of buildpacks.
- Does not support cf CLI `buildpack-administration` commands.
- App developers cannot select a buildpack for their buildpack-based apps.
- Running buildpack-based apps requires the `diego_docker` feature flag to be set.
- The TAS for Kubernetes ingress gateway service may interfere with traffic for other Kubernetes Services in the cluster.
- TAS for Kubernetes cannot use the AWS Elastic Container Registry as its app image registry.
- Does not support upgrading an existing TAS installation to a new version.
- Does not support re-deploying TAS with different credentials.