deps(helm): upgrade ArgoCD & core-services chart versions#128
Closed
oferk0 wants to merge 1 commit into
Closed
Conversation
Bump every core-services Helm chart targetRevision (and the matching cg-devx.metadata chart-version/version labels) to latest stable, and bump the bundled ArgoCD install from v2.14.12 to v3.4.4. Each chart was verified by rendering it with helm template at the new version using the Application's own inline values (29/29 render clean); the ArgoCD kustomize base was verified with kubectl kustomize (71 resources, image v3.4.4). Notable bumps: kube-prometheus-stack 72.6.2 -> 87.1.0 and prometheus- operator-crds 20.0.0 -> 30.0.0 (kept in lockstep, both app v0.92.0); external-secrets 0.16.0 -> 2.6.0; vault 0.26.1 -> 0.33.0; velero 7.2.1 -> 12.0.3; loki 6.30.0 -> 7.0.0; harbor 1.16.3 -> 1.19.1; cert-manager 1.17.2 -> 1.20.2; ingress-nginx 4.12.2 -> 4.15.1; argo-workflows 0.45.15 -> 1.0.17; backstage 1.6.0 -> 2.8.2; kyverno + kyverno-policies 3.4.1 -> 3.8.x (lockstep); keda 2.17.1 -> 2.20.1; trivy-operator 0.28.1 -> 0.33.2; gpu-operator 24.3.0 -> 26.3.2; cluster-autoscaler 9.46.6 -> 9.58.0; gitlab-runner 0.77.2 -> 0.90.0; plus atlantis, tracee, external-dns, reloader, promtail, perfectscale exporter/psc-autoscaler. Values migrations required by the upgrades: - backstage v2 chart: removed image.debug (rejected by the chart schema). Held at the latest patch of the current major line rather than jumping a disruptive product/transitional release (same conservative rationale as the EKS/aws and GKE/google decisions): - kubecost cost-analyzer -> 2.8.6 (2.9.x is a transitional 'agent upgrade prep' release that intentionally refuses to render; no 3.x exists yet). - sonarqube -> 10.8.1 (the chart's 2025/2026 calendar-versioned line is a SonarQube product-major change that also breaks the pinned plugin set and adds a required monitoringPasscode secret). NOTE: helm template confirms each chart renders with its values, but does not flag value keys silently dropped across major versions. Each app should be reviewed against its upstream upgrade notes via the ArgoCD diff before sync.
|
Warning Review limit reached
More reviews will be available in 59 minutes and 6 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. For paid Pro and Pro+ PR reviews, CodeRabbit uses rolling per-developer review limits. Reviews become available again as older review attempts age out of the rolling limit window. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (29)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps 28 chart
targetRevisions (+ metadata labels) to latest stable and ArgoCD v2.14.12→v3.4.4. CRD/operator pairs kept in lockstep (prometheus-operator-crds 30 ↔ kube-prometheus-stack 87; kyverno ↔ kyverno-policies 3.8).Verified: 29/29 charts render via
helm templatewith their inline values; ArgoCDkubectl kustomizebuilds (71 resources).Notable: external-secrets 0.16→2.6, vault 0.26→0.33, velero 7→12, loki 6→7, harbor 1.16→1.19, cert-manager 1.17→1.20, backstage 1.6→2.8 (removed
image.debug).Held to latest patch of current line: kubecost 2.8.6 (2.9 is a non-rendering upgrade-bridge), sonarqube 10.8.1 (2026 line is a product-major + plugin break).
helm templatecan't catch value keys silently dropped across majors — review each app's upgrade notes via the ArgoCD diff before sync.