-
Notifications
You must be signed in to change notification settings - Fork 63
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
Devfile registry air gap/offline installation #329
Comments
Docs JIRA issue: https://issues.redhat.com/browse/RHDEVDOCS-2872 |
Support for offline/airgap is a vital requirement for getting any of this new registry stuff into CRW, as CRW registry builds are by default offline so they can be used behind an airgap/proxy. Please don't forget about this requirement when designing how to build your registries. |
We should also review how the devfile library can access offline parent resources from the registry, especially since a git clone is being done |
Adding this to triage as there seems to be criteria still being worked out. cc: @elsony |
It is already documented in the design doc. See section 1 i. |
Added acceptance criteria |
#1203 - merged which now allows starter projects to be downloaded and the devfiles updated to use the offline starter projects #1220 - will take into consideration all the uri paths and download them to the stack directory devfile/registry#197 - entry point for creating the offline registry image and will be merged after all the child tasks are completed |
A devfile refers to various resources, e.g. container images, projects, and starter projects. The current devfile registry currently does not store those supporting resources as part of the registry. This means that the user will need to have access to those resources when using those devfiles. This item adds support to install a devfile registry in an air-gapped environment.
Design doc: https://docs.google.com/document/d/15PpUGiWOXjfQ5GtJFPHp0cG73jtpmw1H9AkCrnJVD2E/edit?usp=sharing
Acceptance criteria:
Related Issues
Child issues for this EPIC:
The text was updated successfully, but these errors were encountered: