fix(self-managed): bump ess-api chart pin to 1.7.2 - #828
Conversation
Pick up the latest ESS API chart release in the self-managed stack. The ess-api release was pinned to 1.7.0; move it to 1.7.2 so a stack install deploys the current chart (which aligns the ESS app image via appVersion).
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe self-managed core Helmfile updates the ChangesESS API release
Estimated code review effort: 1 (Trivial) | ~2 minutes Mergeability Score: 🔵 Low · up to This change updates the ESS API chart pin from 1.7.0 to 1.7.2. It is low risk, but installations can fail if chart 1.7.2 is not yet available in the configured OCI source, so that dependency requires explicit owner awareness before deployment. Possibly related PRs
Suggested labels: Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
TL;DR
Bump the
ess-apichart version pinned by the self-managed stack from1.7.0to1.7.2so a stack install pulls the current ESS API chart.Why
The self-managed Helmfile pins each service chart by version. The
ess-apirelease was still on1.7.0. The ESS chart line has moved forward (appVersion aligned to the ESS0.4.13service image), so the stack should consume the newer chart.What changed
deploy/stacks/self-managed/helmfile.d/02-core.yaml.gotmpl:ess-apireleaseversion: 1.7.0->1.7.2. No other releases touched.Customer Release Notes
Self-managed stack now deploys ESS API chart 1.7.2.
Plan Summary
Single chart-version pin change. No template or values changes. Rendered topology is unchanged apart from the ess-api chart version.
Usage
Not applicable (picked up automatically by
make -C deploy/stacks/self-managed install).Testing
helm lint/helm templatefor the ess-api chart pass locally. Full stack render/install requires NGC credentials and a k3d cluster (not run here). Thedeploy/stacks/self-managedOCI pull ofhelm-nvcf-ess-api:1.7.2requires that chart version to be published in the registry.Notes
Depends on ESS chart
1.7.2being published to the OCI registry. That release is produced by the ess-helm release automation once #791 (which bumps the chart appVersion) merges and tagsdeploy/helm/encrypted-secret-store/v1.7.2. Do not merge/deploy this stack bump before1.7.2is available in the registry, or the install will fail to pull the chart.References
None
Related Pull Requests
Dependencies
None
Issues
Relates to #747
Summary by CodeRabbit