[BUG]How yurtctl convert
can better close the nodelifecycle controller
(kube-controller-manager
)?
#391
Labels
kind/bug
kind/bug
What happened:
When excuting the command
yurtctl convert
, the clusterrolebindingsystem:controller:node-controller
will be deleted to turn off thenodelifecycle controller
(inkube-controller-manager
).However, the flowing questions will appear afterwards:
system:controller:node-controller
can't work normally.eg: issue: [BUG] flannel not success when convert k8s #380
system:controller:node-controller
.Issue: [Question]Questions about clusterrolebinding system:controller:node-controller being deleted. #347
What you expected to happen:
yurtctl convert
doesn't turn offnodelifecycle controller
by deleting clusterrolebindingsystem:controller:node-controller
. And it can support the high availability ofkube-controller-manager
.How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Solutions currently proposed:
When executing
yurtctl convert
, 1) Ifkube-controller-manager
is deployed through static file/etc/kubernetes/manifests/kube-controller-manager.yaml
: Create jobs for all candidates to modify this file to turn offnodelifecycle controller
. 2) Ifkube-controller-manager
is not deployed through a static file: Modifykube-controller-manager
template directly.And this scheme has the following problems:
If the kube-controller-manager is not deployed through a static file (/etc/kubernetes/manifests/), modify
kube-controller-manager
template directly will lead to the runtime template is inconsistent with the user's local yaml file.Environment:
kubectl version
):cat /etc/os-release
):uname -a
):others
/kind bug
The text was updated successfully, but these errors were encountered: