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

Update Documentation to say "Control Plane" #274

Open
christianh814 opened this issue Feb 9, 2022 · 1 comment
Open

Update Documentation to say "Control Plane" #274

christianh814 opened this issue Feb 9, 2022 · 1 comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed

Comments

@christianh814
Copy link
Contributor

Update all documentation, code/playbooks and graphics to say "control plane" instead of "master" as this change is already happening upstream.
@christianh814 christianh814 added documentation Improvements or additions to documentation enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed labels Feb 9, 2022
@semlohnayr semlohnayr mentioned this issue Feb 11, 2022
Open
pbmoses added a commit to pbmoses/ocp4-helpernode that referenced this issue Feb 12, 2022
@pbmoses
Update Documentation to say "Control Plane" redhat-cop#274
ffe4176 
Control Plane utilized where appropriate controlplane utilized in code.
@pbmoses
Copy link

pbmoses commented Feb 12, 2022

proposing a common method to be utilized.

In Docs where a description is desired = Control Plane
In code examples = controlplane

Please advise, I will begin to refactor these.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
documentation Improvements or additions to documentation enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@christianh814 @pbmoses