From 2b70b383cde8858e060f2cc448ecff2a6f230e0d Mon Sep 17 00:00:00 2001
From: Ciprian Hacman <ciprian@hakman.dev>
Date: Thu, 13 May 2021 15:09:48 +0300
Subject: [PATCH] Remove etcd-manager certificate expiration advisory

All affected versions are now EOL.
---
 README.md | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/README.md b/README.md
index 7c7f06b14a..3c849cf61f 100644
--- a/README.md
+++ b/README.md
@@ -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.