Open raykrueger opened 1 year ago
That is why I created https://github.com/oras-project/oras/issues/730
There are kind of extreme work around like you could run your registry on a computer and move the computer into the air gapped env. Obviously, that would not be allowed in some env.
I was hoping to upstream that to oras, but if that fails, we could use the code in my POC link in that issue.
related issue: https://github.com/aws/eks-anywhere/issues/5396
The code in the draft PRs I mentioned are what we should use if we are going to implement this. It will take a while to get this through the oras community and I'm kind of busy now to push that.
The code in the draft PRs I mentioned are what we should use if we are going to implement this. It will take a while to get this through the oras community and I'm kind of busy now to push that.
What I mean by that is if we want a download packages
right now, we should just take the code from the draft PR and use it. If we can wait, it should get pushed through eventually.
What would you like to be added: As a cluster admin I want to be able to pull curated packages from the internet, switch to my private network, and push to a private registry.
Why is this needed: The import images process allows for a pull from the internet, disconnect, connect to airgapped environment and push to private registry process. The curated packages import does this in one-shot pull/push process. Which means we cannot support an airgapped install.