-
|
Is anyone currently solving for this particular issue? In this scenario we have a completely blank environment, no existing infrastructure - aka no container registries to pull from. In an airgapped environment this makes it difficult to get Talos going without implementing some sort of stop-gap registry for Talos to just start. The reason why this is a bit of a conundrum is that I'd rather Talos host the registry that would then be used in standing up subsequent clusters, but in order for Talos to run, I need a registry. A bit of a circular loop here aka chicken and the egg. If there was a way to preload a tarball of images to containerd on startup that would effectively fix this issue, but I don't think this is currently something that is offered. Is this something that is completely out of scope? Is anyone else running into this problem or has solved this particular problem? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
We have some plans for Talos 1.9 to implement an image cache, but that would only cover layers, not manifests most probably in the first iteration. So it still requires registry access, but only to fetch manifests. Right now I would say the easiest is to have the registry like described in the docs |
Beta Was this translation helpful? Give feedback.
-
|
Fair enough, thank you for the reply! |
Beta Was this translation helpful? Give feedback.
We have some plans for Talos 1.9 to implement an image cache, but that would only cover layers, not manifests most probably in the first iteration.
So it still requires registry access, but only to fetch manifests.
Right now I would say the easiest is to have the registry like described in the docs