-
Notifications
You must be signed in to change notification settings - Fork 401
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
layering: pod-like MachineImage idea #3327
Comments
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closing this issue. In response to this:
Instructions 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. |
I've been trying to sketch this out in chats around OCP CoreOS Layering.
Right now the API to interact is basically "override osImageURL" - all the rest of the MCO machinery then works in the same way it does today. Most notably on this topic for example, the MCO (node controller) still owns choosing the node rollout order (i.e. which nodes get the update in what order). This relates to #3009 as well as #2163 etc.
Once we have the "build controller" aspect of the MCO; actually ideally once we have #3137 - the admin could instead even more fully "take the wheel" and own creating something that is very much like a cut-down
Pod
to a node or a node selector, which contains the OS image they want to use:Here we're using
nodeName
to assign an image to a particular node.But, it should work to use all standard mechanisms to assign pods to nodes, for example node selectors:
I'd strawman out that once a
MachineImage
CRD is created, the MCO stops rolling out images on its own for all nodes in the pool which has any matchingMachineImage
or so.Pull secret
Also, we should add a pull secret to this CRD which allows configuring that.
The text was updated successfully, but these errors were encountered: