From eeba8ccbb8e7ee3fa5c369f9163992982d735022 Mon Sep 17 00:00:00 2001 From: Tim Bannister Date: Sat, 9 Dec 2023 19:58:15 +0000 Subject: [PATCH] Revise article wording --- .../2023-12-14-disabling-in-tree-cloud-provider-goes-beta.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/content/en/blog/_posts/2023-12-14-disabling-in-tree-cloud-provider-goes-beta.md b/content/en/blog/_posts/2023-12-14-disabling-in-tree-cloud-provider-goes-beta.md index 638e291390..5a3fc0214d 100644 --- a/content/en/blog/_posts/2023-12-14-disabling-in-tree-cloud-provider-goes-beta.md +++ b/content/en/blog/_posts/2023-12-14-disabling-in-tree-cloud-provider-goes-beta.md @@ -9,8 +9,9 @@ slug: cloud-provider-integration-changes For Kubernetes v1.29, you need to use additional components to integrate your Kubernetes cluster with a cloud infrastructure provider. By default, Kubernetes -v1.29 disallows components configured with legacy compiled-in cloud provider -integrations. +v1.29 components **abort** if you try to specify integration with any cloud provider using +one of the legacy compiled-in cloud provider integrations. If you want to use a legacy +integration, you have to opt back in - and a future release will remove even that option. In 2018, the [Kubernetes community agreed to form the Cloud Provider Special Interest Group (SIG)][oldblog], with a mission to externalize all cloud provider