From 12056babf56b92e2c1823f055711cb17d1709e3c Mon Sep 17 00:00:00 2001 From: "xin.li" Date: Sun, 8 Dec 2024 15:49:06 +0800 Subject: [PATCH] [zh-cn]sync controller-manager-leader-migration Signed-off-by: xin.li --- .../administer-cluster/controller-manager-leader-migration.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/content/zh-cn/docs/tasks/administer-cluster/controller-manager-leader-migration.md b/content/zh-cn/docs/tasks/administer-cluster/controller-manager-leader-migration.md index eba3ea5577e02..3e5a18c0fc0e6 100644 --- a/content/zh-cn/docs/tasks/administer-cluster/controller-manager-leader-migration.md +++ b/content/zh-cn/docs/tasks/administer-cluster/controller-manager-leader-migration.md @@ -186,6 +186,7 @@ Leader Migration can be enabled without a configuration. Please see kind: LeaderMigrationConfiguration apiVersion: controllermanager.config.k8s.io/v1 leaderName: cloud-provider-extraction-migration +resourceLock: leases controllerLeaders: - name: route component: kube-controller-manager @@ -208,6 +209,7 @@ between both parties of the migration. kind: LeaderMigrationConfiguration apiVersion: controllermanager.config.k8s.io/v1 leaderName: cloud-provider-extraction-migration +resourceLock: leases controllerLeaders: - name: route component: * @@ -260,6 +262,7 @@ which has the same effect. kind: LeaderMigrationConfiguration apiVersion: controllermanager.config.k8s.io/v1 leaderName: cloud-provider-extraction-migration +resourceLock: leases controllerLeaders: - name: route component: cloud-controller-manager @@ -400,6 +403,7 @@ controllers. kind: LeaderMigrationConfiguration apiVersion: controllermanager.config.k8s.io/v1 leaderName: cloud-provider-extraction-migration +resourceLock: leases controllerLeaders: - name: route component: *