-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
baremetal: Migrate Ironic services to upstream images #2090
Comments
/label platform/baremetal |
It looks like all the ironic and image downloading containers are in the releases now:
How would we move it to the static pods? I think we want to ensure an ordering - right? Downloading of images needs to happen before Ironic starts, can that be controlled in MCO? Is this something we need to deal with later? |
Those image names are going to be changing shortly. See openshift/release#4623 and openshift/machine-api-operator#370 |
@stbenjam I raised #2251 to investigate how we migrate to staticpods, I'm unclear if MCO Is an option since we only want this to run on the boostrap VM? I know @cybertron did the work to move the DNS services (which do have a slightly different configuration on the bootstrap VM) to MCO, perhaps he can provide some pointers before we dig into it. |
Yeah, we have separate networking service configs for bootstrap, so it should be possible. You can see the change I made to do that in openshift/machine-config-operator@ec7ef01 Note in particular that bootstrap pod definitions go in manifests/. We also have some in templates/, but those are for the masters and workers. As far as ordering, could you do the image download as an initContainer? We use one to generate our config before we start the service. Seems like that would serve your purposes too. |
The integration proposed via #2079 currently depends on some upstream images, because those in the openshift org are still in-progress.
This issue is to track moving to the correct OCP builds of these containers, and also similar to #2067 we should look at options to move to a staticpod, and perhaps also the MCO instead of the current systemd/script approach.
Ideally I'd like to not block the initial experimental support on this, so I'm raising this as a separate issue to #2060 and we'll address these issues via follow-up PRs
The text was updated successfully, but these errors were encountered: