*: Update "MachinePool" -> "MachineConfigPool" and similar#513
Conversation
There seems to have been some initial uncertainty about what this would be called, with MachinePool first landing in 30d522f (docs: add initial documentation of design, 2018-07-25) and MachineConfigPool first landing in cfc9660 (pkg/apis: add machineconfiguration.openshift.io apis, 2018-07-26, openshift#2). This commit consolidates us around MachineConfigPool, except for the machine-pools/ bootstrap path (since changing that would require consumer updates).
|
@wking I still see |
|
/hold |
I'm fine diverging. The installer's |
|
Also since this is not a bug fix it seems like this should be against the 4.1 branch @runcom ? |
|
Most of the changes look trivial but I'm fine deferring to 4.1. |
|
I don't see a reason not to do this now. /lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cgwalters, wking 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 cancel |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
2 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest |
There seems to have been some initial uncertainty about what this would be called, with
MachinePoolfirst landing in 30d522f andMachineConfigPoolfirst landing in cfc9660 (#2). This commit consolidates us aroundMachineConfigPool, except for themachine-pools/bootstrap path (since changing that would require consumer updates).