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.

Sign up for GitHub

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

Jump to bottom

Nomenclature: Master to Control Plane #33

Open
ralgozino opened this issue Oct 18, 2022 · 1 comment
Open

Nomenclature: Master to Control Plane #33

ralgozino opened this issue Oct 18, 2022 · 1 comment
Assignees
@stefanoghinelli

Comments

@ralgozino
Copy link
Member

ralgozino commented Oct 18, 2022 •
edited
Loading

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
Copy link
Member

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@stefanoghinelli stefanoghinelli

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ralgozino @stefanoghinelli