-
Notifications
You must be signed in to change notification settings - Fork 8
✨ Add registry_mirrors feature #197
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
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Nils Arnold <arnold@aov.de>
|
I like this. |
|
Needs rebase. |
|
This was not pulled into scs2, but we could add it (with the right default) in a non breaking way. |
Yes, but I see some challenges here which seem to be a string of problems. First the patch requires containerd. This is not optimal, but also not too bad because because the images we used to use have containerd. But those images are no longer available as they were before. I think we should provide them ourselves now. Either we prebuild them with image-builder or diskimage-builder or we just install the packages as we did before in our first ClusterClass tests. Actually I prefer the latter, even it's not as reproducible, but since we missed the immutability anyway we won't lose much value. Additionally we can make better use of the builtin variables. Back to this PR: we can then choose which container runtime to install in the |
|
@jschoone Is it already the case that new images are no longer provided by OSISM? E.g. I am missing the ubuntu-2404-kube-v1.33.6 image for the scs2 v3 ClusterStack. |
|
Ok @Nils98Ar showed me it works now with the new location of the images. Yesterday it didn't when I wanted to provide the ORC image resource. That saves time. |
|
Add a PR regarding images: #245 |
What this PR does / why we need it:
Add
ClusterClassvariableregistry_mirrorsto openstack scs ClusterStack for configuring registry mirrors in containerd.Example value:
TODOs: