github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-07-29 14:37:00 +00:00
Code Issues Projects Releases Wiki Activity

CHANGELOG: Add known issue for GLBC Health Check overwrite.

Browse Source
This commit is contained in:
Anthony Yeh 2017-06-15 17:19:51 -07:00
parent dd9e82221c
commit fdb857ea2f
No known key found for this signature in database
GPG Key ID: 339F46A383E6ED08
1 changed files with 24 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
CHANGELOG.md
View File

@ -16,6 +16,7 @@
- [Action Required](#action-required-1)
- [Other notable changes](#other-notable-changes-1)
- [v1.6.5](#v165)
- [Known Issues for v1.6.5](#known-issues-for-v165)
- [Downloads for v1.6.5](#downloads-for-v165)
- [Client Binaries](#client-binaries-2)
- [Server Binaries](#server-binaries-2)
@ -31,6 +32,7 @@
- [Action Required](#action-required-2)
- [Other notable changes](#other-notable-changes-3)
- [v1.6.4](#v164)
- [Known Issues for v1.6.4](#known-issues-for-v164)
- [Downloads for v1.6.4](#downloads-for-v164)
- [Client Binaries](#client-binaries-4)
- [Server Binaries](#server-binaries-4)
@ -769,6 +771,17 @@ filename | sha256 hash
[Documentation](https://docs.k8s.io) & [Examples](https://releases.k8s.io/release-1.6/examples)
## Known Issues for v1.6.5
* If you use the [GLBC Ingress Controller](https://github.com/kubernetes/ingress/tree/master/controllers/gce),
upgrading an existing pre-v1.6.4 cluster to Kubernetes v1.6.5 will cause an unintentional
[overwrite of manual edits to GCP Health Checks](https://github.com/kubernetes/ingress/issues/842)
managed by the GLBC Ingress Controller. This can cause the health checks to start failing,
requiring you to reapply the manual edits.
* This issue does not affect clusters that were already running Kubernetes v1.6.4 or higher.
* This issue does not affect Health Checks that were left in the configuration
[originally set by the GLBC Ingress Controller](https://github.com/kubernetes/ingress/tree/master/controllers/gce#health-checks).
## Downloads for v1.6.5
@ -1065,6 +1078,17 @@ filename | sha256 hash
[Documentation](https://docs.k8s.io) & [Examples](https://releases.k8s.io/release-1.6.3/examples)
## Known Issues for v1.6.4
* If you use the [GLBC Ingress Controller](https://github.com/kubernetes/ingress/tree/master/controllers/gce),
upgrading an existing cluster to Kubernetes v1.6.4 will cause an unintentional
[overwrite of manual edits to GCP Health Checks](https://github.com/kubernetes/ingress/issues/842)
managed by the GLBC Ingress Controller. This can cause the health checks to start failing,
requiring you to reapply the manual edits.
* This issue does not affect clusters that start out with Kubernetes v1.6.4 or higher.
* This issue does not affect Health Checks that were left in the configuration
[originally set by the GLBC Ingress Controller](https://github.com/kubernetes/ingress/tree/master/controllers/gce#health-checks).
## Downloads for v1.6.4