-
Notifications
You must be signed in to change notification settings - Fork 170
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
Use Iron Bank images for the PLG stack #214
Comments
@RothAndrew for this, #213 and #215 are we looking for getting/using the current versions we are using in DockerHub into IB? |
If IB has the images we need that will work for us. We should definitely make it a priority to get the latest versions of everything into IB but that doesn’t need to block this. The bigger priority is just that IB is the source for those images. |
We actually need to discuss this some more and make a plan, we have some housekeeping to do post-mega pr on how we manage arm vs amd and IB has no arm support at all because it's super lame. I'm less worried about pgl than gitea or registry2 for init because those would be used with a Big Bang example--the only place someone would care about iron bank images. And between those two--we won't be able to use iron bank at all with the new injector stuff until iron bank uses an appropriate base image. Iron bank takes a 9 mb image tarball and makes it over 100 mb by using the wrong base image. |
kicking this back to planned so we can sort through how we want to handle IB images for the init package. |
Closing IB stories for init package until we have a better plan, will consolidate into a new story. |
Currently we use PLG images from DockerHub. We need to get them from Iron Bank.
grafana/loki
grafana/promtail
grafana/grafana
kiwigrid/k8s-sidecar
The text was updated successfully, but these errors were encountered: