From 3bea36ba16244d3d85c07fb67525e56ec77940dc Mon Sep 17 00:00:00 2001 From: Alvaro Aleman Date: Mon, 12 Aug 2019 20:15:13 +0200 Subject: [PATCH] Api deprecation blogpost: Include minimum kube version for ingress from networking apigroup (#15740) --- .../blog/_posts/2019-07-18-some-apis-are-being-deprecated.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/blog/_posts/2019-07-18-some-apis-are-being-deprecated.md b/content/en/blog/_posts/2019-07-18-some-apis-are-being-deprecated.md index 549dfdb72f..bc9a3f3e15 100644 --- a/content/en/blog/_posts/2019-07-18-some-apis-are-being-deprecated.md +++ b/content/en/blog/_posts/2019-07-18-some-apis-are-being-deprecated.md @@ -34,8 +34,8 @@ from **extensions/v1beta1**, **apps/v1beta1**, or **apps/v1beta2** in **v1.16**. * Migrate to the apps/v1 API, available since v1.9. Existing persisted data can be retrieved/updated via the apps/v1 API. * Ingress: will no longer be served from **extensions/v1beta1** in **v1.18**. - * Migrate to the networking.k8s.io/v1beta1 API. Existing persisted data can be - retrieved/updated via the networking.k8s.io/v1beta1 API. + * Migrate to the networking.k8s.io/v1beta1 API, serving Ingress since v1.14. + Existing persisted data can be retrieved/updated via the networking.k8s.io/v1beta1 API. # What To Do