Nomenclature: Master to Control Plane

sighupio / fury-kubernetes-on-premises

Kubernetes Fury Distribution On-Premises Core Module: Create on-prem Kubernetes Clusters

BSD 3-Clause "New" or "Revised" License

7 stars 4 forks source link

Open ralgozino opened 2 years ago

ralgozino commented 2 years ago

Kubernetes and Kubeadm are moving away from using the term master to using control plane instead.

We should eventually align with upstream in the nomenclature to avoid confusion.

stefanoghinelli commented 2 weeks ago

I did a grep of the term master in the repo to check all the points that need to be eventually aligned. The change mainly affects:

Roles:
- need to update task names
HAProxy:
- backend in haproxy.conf.j2
- server names master1, master2, master3
- keepalived variables with master references
Examples:
- groups defined as master in hosts.yaml
- hostnames
- task names and comments in playbooks
READMEs

Should we include these alignments in the upcoming v1.30 release?