Page MenuHomePhabricator

Proposal: ditching the master name in kubernetes servers
Closed, ResolvedPublic


The upstream kubernetes devs are mostly now referring to the "master" as the "control plane" node. It is still called master in the API for purposes of the node taints (and probably will be for the foreseeable future), but continuing my effort to remove the terms master and slave where we can get away with it, we could follow suit and deploy the new cluster (when it is ready), using the name "tools-k8s-control-01/2/3" instead since we are replacing the nodes anyway.

This is just to bring it up for discussion, and if accepted, update docs once we are ready to deploy.

Event Timeline

At this point, I'm going to leave this task open basically for just long enough for us to build new control plane nodes in toolsbeta. I don't think it requires us tearing down the test cluster for now.

I can easily start changing names in puppet for the new material, though.

Change 530186 had a related patch set uploaded (by Bstorm; owner: Bstorm):
[operations/puppet@production] toolforge: rebranding k8s control plane to control

Change 530186 merged by Bstorm:
[operations/puppet@production] toolforge: rebranding k8s control plane to control

I think we all agreed on this and next version of k8s already uses 'control' rather than 'master'.