-
Epic
-
Resolution: Done
-
Major
-
None
-
None
-
declarative index config upstream tooling
-
Upstream
-
False
-
False
-
To Do
-
OCPSTRAT-425 - Enable file-based Catalog for flexible and lightweight catalog maintenance
-
OCPSTRAT-425Enable file-based Catalog for flexible and lightweight catalog maintenance
-
0% To Do, 0% In Progress, 100% Done
-
Undefined
-
M
Epic Goal
- Upstream adoption of OLM packaging tools with popular CI infrastructure like GitHub Actions
- Extend support for building operator artifacts with declarative index configs
- Initiate Community Operators adoption of file based catalogs
Why is this important?
- there is currently only rough documentation on OLMs packaging tools
- there is fragmentation in the guidance around how Operator developers are supposed to build release artifacts (opm vs. operator-sdk)
- there is little to no guidance on how to publish release artifacts as part of a catalog
Acceptance Criteria
- GitHub actions that can build Operator bundles from bundle metadata
- GitHub actions that can build Operator catalogs from declarative index
- Documnetation for both actions
- Instructions on how to build an example GitHub Action based pipeline to automatically create bundle artifacts and automatically publish them to a catalog based on the above
Optional achievements
- Tekton Tasks that can build operator bundles from bundle metadata published on Tekton Hub
- Tekton Tasks that can build operator catalogs from declarative index published on Tekton Hub
Done Checklist
- CI - CI is running, tests are automated and merged.
- DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
- DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
- is blocked by
-
OPRUN-2211 Operator Authors have a clean veneer for releasing bundles (File based config/declarative config)
- Closed
- relates to
-
OPECO-2111 Scaffold git-friendly automated build workflows for File-based Catalog
- Closed