Remove etcd-manager certificate expiration advisory

All affected versions are now EOL.
This commit is contained in:
Ciprian Hacman 2021-05-13 15:09:48 +03:00
parent 7b0487066e
commit 2b70b383cd
1 changed files with 0 additions and 4 deletions

View File

@ -8,10 +8,6 @@
The easiest way to get a production grade Kubernetes cluster up and running.
## 2020-05-06 etcd-manager Certificate Expiration Advisory
kOps versions released today contain a **critical fix** to etcd-manager: 1 year after creation (or first adopting etcd-manager), clusters will stop responding due to expiration of a TLS certificate. Upgrading kOps to 1.15.3, 1.16.2, 1.17.0-beta.2, or 1.18.0-alpha.3 is highly recommended. Please see the [advisory](./docs/advisories/etcd-manager-certificate-expiration.md) for the full details.
## What is kOps?
We like to think of it as `kubectl` for clusters.