-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
5
-
False
-
None
-
False
-
-
Owner: Architect:
This story is with reference to https://issues.redhat.com/browse/RFE-4715 . We would like to mirror the helm charts present in our repository to a desired location in case of disconnected environment.
Story (Required)
With the helm repos being added as a replacement to the samples operator there is a requirement to provide a systematic way to identify which images must be mired into the air gap with minimal effort on the customer.
In a disconnected environment the customers are making use of https://github.com/openshift/oc-mirror for image streams. We would like to create a similar tooling which mirrors the helm charts available in openshift repository to desired location.
Background (Required)
This story is with reference to https://issues.redhat.com/browse/RFE-4715 . We would like to mirror the helm charts present in our repository to a desired location in case of disconnected environment.
Approach(Required)
_<Description of the general technical path on how to achieve the goal of
the story. Include details like json schema, class definitions>_
Work on a script which copy the helm charts on the openshift repository to a desired server(before the user is in a disconnected environment the mirroring is to be performed)
Investigate on https://github.com/openshift/oc-mirror to see if that can be modified
Access the source repo https://charts.openshift.io/index.yaml
Pull the charts using the http client
Prepare another helm repo by taking in the pulled helm charts and push them to a new desired destination
Document the steps to be followed to mirror the repository
Acceptance Criteria
_<Provides a required and minimum list of acceptance tests for this story.
More is expected as the engineer implements this story>_
Development: Yes
QE:
Documentation: Yes (needs-docs|upstream-docs / no-doc)
Upstream: <Inputs/Requirement details: Concept/Procedure>/ Not
Applicable
Downstream: <Inputs/Requirement details: Concept/Procedure>/ Not
Applicable
Release Notes Type: <New Feature/Enhancement/Known Issue/Bug
fix/Breaking change/Deprecated Functionality/Technology Preview>
INVEST Checklist
Dependencies identified
Blockers noted and expected delivery timelines set
Design is implementable
Acceptance criteria agreed upon
Story estimated
v
Legend
Unknown
Verified
Unsatisfied