-
Notifications
You must be signed in to change notification settings - Fork 1.5k
*: replace master/worker terms with control-plane/compute #1227
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
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: staebler The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/hold Pending feature exception approval. |
|
/hold cancel The feature exception for this has been approved. |
/retest |
|
openshift.service
Bootstrapping did not complete because the openshift service could not create the |
|
/retest |
Rate-limit errors /test e2e-aws |
Rename the Master and Worker machine assets to Control Plane and Compute, respectively. This is part of the overall effort to replace the terms master and worker with control plane and compute throughout the installer.
Pass in as a variable to terraform the name of the control plane machine pool. This is part of the overall effort to replace the terms master and worker with control plane and compute throughout the installer.
Rename the Master and Worker ignition assets to Control Plane and Compute, respectively. This is part of the overall effort to replace the terms master and worker with control plane and compute throughout the installer.
Replace references to master and worker in the aws terraform with control-plane and compute, respectively. This is part of the overall effort to replace the terms master and worker with control plane and compute throughout the installer.
Use the MachineRole type to differentiate between control-plane machines and compute machines. This is part of the overall effort to replace the terms master and worker with control plane and compute throughout the installer.
This is part of the overall effort to replace the terms master and worker with control plane and compute throughout the installer.
…pute This is part of the overall effort to replace the terms master and worker with control plane and compute throughout the installer.
This is part of the overall effort to replace the terms master and worker with control plane and compute throughout the installer.
This is part of the overall effort to replace the terms master and worker with control plane and compute throughout the installer.
The Master Machines, Worker Machines, Master Ignition, and Worker Ignition files were renamed to Control Plane Machines, Compute Machines, Control Plane Ignition, and Compute Ignition, resepctively. Consequently, the dependency graph needed to be updated. Generated with: $ openshift-install graph | dot -Tsvg >docs/design/resource_dep.svg using: $ dot -V dot - graphviz version 2.40.1 (20161225.0304)
/retest |
Failure when cleaning up bootstrap resources. /retest |
I'm a fan but...it's not just the installer but (eventually) OpenShift in general right? We're going to have...a lot of work to do for that. In the MCO for example renaming everything as part of an upgrade would get...tricky. |
|
@staebler: PR needs rebase. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
My expectation is that, yes, eventually OpenShift in general will switch to using the control plane and compute terms. However, I would not expect that an update would change the names of existing resources. Code should generally not be relying on the names of resources but instead on labels on those resources. For the MCO in particular, I'm not sure what more would need to be done beyond serving the config from, for example, both master and control-plane endpoints. Can you elaborate on some other things in upgrading after terms change that you anticipate being tricky? |
|
/hold Hold for 4.1. |
Replace references to master and worker with control plane and compute throughout the installer.
Remaining references:
sigs.k8s.io/cluster-api-machine-roleandsigs.k8s.io/cluster-api-machine-typestill use themasterandworkervalues./config/masterand/config/worker.system:masters.