Remove deprecated --cluster-concurrency flag in CABPK

Signed-off-by: Stefan Büringer [email protected]

Author: sbueringer

bootstrap/kubeadm/main.go

@@ -87,7 +87,6 @@ var (
 	managerOptions              = flags.ManagerOptions{}
 	logOptions                  = logs.NewOptions()
 	// CABPK specific flags.
-	clusterConcurrency       int
 	clusterCacheConcurrency  int
 	kubeadmConfigConcurrency int
 	skipCRDMigrationPhases   []string
@@ -130,10 +129,6 @@ func InitFlags(fs *pflag.FlagSet) {
 	fs.BoolVar(&enableContentionProfiling, "contention-profiling", false,
 		"Enable block profiling")
 
-	fs.IntVar(&clusterConcurrency, "cluster-concurrency", 10,
-		"Number of clusters to process simultaneously")
-	_ = fs.MarkDeprecated("cluster-concurrency", "This flag has no function anymore and is going to be removed in a next release. Use \"--clustercachetracker-concurrency\" instead.")
-
 	fs.IntVar(&clusterCacheConcurrency, "clustercache-concurrency", 100,
 		"Number of clusters to process simultaneously")
 

docs/book/src/developer/providers/migrations/v1.12-to-v1.13.md

@@ -52,6 +52,7 @@ Any feedback or contributions to improve following documentation is welcome!
 ## Removals
 
 - The deprecated `ClusterCache.GetClientCertificatePrivateKey` method has been removed.
+- The deprecated `--cluster-concurrency` CABPK command-line flag has been removed 
 
 ## Suggested changes for providers