-
Notifications
You must be signed in to change notification settings - Fork 2.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
auto update without registry on local images #9088
Comments
The majority of the "production" use cases seem to prefer separating builds from runtime environments. That said, I like this idea and it seems really useful for certain types of use cases. This would be valuable for my home systems and I can see other development-ish use cases where this would be helpful. Agreed that short names are common for local use. I don't have a strong opinion on good options here, but would requiring "localhost/[name]" be an acceptable compromise? requiring a local policy feels cumbersome, but it's possible that's a better option. |
+1 Ben. Also, since we have the secure short names feature now (or will), I think this could probably be done in a way has defense in depth and prevents an attack from a man in the middle. I could also see this being used in an environment with really slow internet connection. It might be cheaper to deliver a Dockerfile/Containerfile out and have the image build from some local cache of packages. It's probably an edge case, but could be really convenient if you happen to be a user with that edge case. |
A friendly reminder that this issue had no activity for 30 days. |
@vrothberg Is this is issue you wanted @ParkerVR to look at? |
@rhatdan touched based with @vrothberg on this and will discuss more in depth tmmr |
A friendly reminder that this issue had no activity for 30 days. |
Implemented in #10063. |
/kind feature
Description
After a private chat with a user on auto updates, it became clear that auto updates could also be applied without having a container registry. For instance, when images built locally, the use case remains the same. Currently, auto updates only work when the image on the remote registry has changed.
There a couple of things to think about:
@fatherlinux @mrguitar ... do you have feedback suggestions?
The text was updated successfully, but these errors were encountered: