Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When existing worker node is made a control plane node , the node gets removed from the cluster. #66

Closed
sangeethah opened this issue Nov 29, 2017 · 1 comment
Assignees
Labels

Comments

@sangeethah
Copy link

rke version v0.0.7-dev

Steps to reproduce the problem:
Created a k8s with 1 controlplane node , 1 etcd and 3 worker nodes.
Updated one of the node in worker plane to become a controlplane node.

When controlplane nodes are getting evaluated:
The updated host, becomes a controlplane node (I do see the system containers relating to control plane being deployed in this host).
Also rolling updates for the nginx-proxy container for all existing worker nodes gets updated with this new host in controlplane node as expetced.

When worker nodes are getting evaluated:
This host gets removed from the k8s cluster.

Expected behavior:
The host should continue to be part of K8s cluster but should be a cotrolplane node.

@sangeethah
Copy link
Author

Tested with rke version v0.0.8-dev

Created a k8s with 2 controlplane node , 1 etcd and 3 worker nodes.
Updated one of the nodes in worker plane to become a control plane node.

Node that was updated to become a control plane , continues to be in part of K8s cluster and becomes a master node as expected. It has all the control plane system containers running it and no nginx-proxy container running in it.

kube-proxy
kubelet
scheduler
kube-controller
kube-api

Also nginx-proxy containers in all existing worker nodes now have this new node programmed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants