-
Task
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
False
-
-
False
-
-
The downstream Helm chart (quay.io/rhdh/chart) currently lacks floating "next" tags, making it difficult to reliably reference the latest chart version in CI/E2E testing.
Current State
- RHDH images have next and next-1.y tags (e.g., next, next-1.9)
- Operator bundle has floating 1.y tags at quay.io/rhdh/rhdh-operator-bundle
- Helm chart only has versioned tags like 1.9-xxx-CI with no floating equivalent
- Current workarounds require parsing RHDH image tags to determine the latest chart version
Proposed Solution
Add floating tags to the downstream Helm chart consistent with RHDH image tagging:
- next - points to the latest build from main branch
- next-1.y - points to the latest build from each release branch (e.g., next-1.9, next-1.10)
This aligns with Armel's preference for explicit next naming (vs just 1.y) so the meaning is clear by just seeing the tag.
Acceptance Criteria
- [ ] Helm chart builds publish a floating next tag pointing to the latest main branch build
- [ ] Helm chart builds publish floating next-1.y tags for each active release branch (e.g., next-1.9, next-1.10)
- [ ] Tags are automatically updated with each new nightly/CI build
- [ ] Tag naming follows RHDH image convention (next, next-1.y) for consistency
- [ ] CI/E2E tests can reference next or next-1.y tags instead of hardcoded versions
- [ ] Documentation updated to reference the new tags for testing purposes
Related Issues
- RHIDP-9139 - [CI] automatically use correct Helm Chart version in e2e
- RHIDP-11546 - Build a new quay.io/rhdh/chart for each new updated index image
- relates to
-
RHIDP-9139 [CI] automatically use correct Helm Chart version in e2e
-
- Refinement
-
-
RHIDP-11546 Build a new quay.io/rhdh/chart (with -CI tag) & operator-bundle for each new updated index image
-
- To Do
-