Skip to content

Commit eeba8cc

Browse files
author
Tim Bannister
committed
Revise article wording
1 parent bfd5750 commit eeba8cc

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

content/en/blog/_posts/2023-12-14-disabling-in-tree-cloud-provider-goes-beta.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,8 +9,9 @@ slug: cloud-provider-integration-changes
99

1010
For Kubernetes v1.29, you need to use additional components to integrate your
1111
Kubernetes cluster with a cloud infrastructure provider. By default, Kubernetes
12-
v1.29 disallows components configured with legacy compiled-in cloud provider
13-
integrations.
12+
v1.29 components **abort** if you try to specify integration with any cloud provider using
13+
one of the legacy compiled-in cloud provider integrations. If you want to use a legacy
14+
integration, you have to opt back in - and a future release will remove even that option.
1415

1516
In 2018, the [Kubernetes community agreed to form the Cloud Provider Special
1617
Interest Group (SIG)][oldblog], with a mission to externalize all cloud provider

0 commit comments

Comments
 (0)