[PR #48] [CLOSED] feat(pyroscope)!: migrate to Helm chart v2.0.1 #313

New issue

Closed

opened 2026-06-08 08:31:28 +00:00 by ryangr0 · 0 comments

ryangr0 commented

2026-06-08 08:31:28 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/webgrip/homelab-cluster/pull/48
Author: @Copilot
Created: 5/19/2026
Status: ❌ Closed

Base: main ← Head: copilot/chore-plan-migration-to-helm-v2-0

📝 Commits (4)

c67fe38 Initial plan
edde5b9 chore(renovate): block Pyroscope major version auto-upgrade (v2.0 breaking changes)
4af6e3b feat(pyroscope)!: migrate to Helm chart v2.0.1 with v1 storage path preserved
305ab39 chore(pyroscope): switch to OCIRepository with SHA digest pinning

📊 Changes

4 files changed (+26 additions, -20 deletions)

View changed files

📝 kubernetes/apps/observability/pyroscope/app/helmrelease.yaml (+9 -8)
➖ kubernetes/apps/observability/pyroscope/app/helmrepository.yaml (+0 -11)
📝 kubernetes/apps/observability/pyroscope/app/kustomization.yaml (+1 -1)
➕ kubernetes/apps/observability/pyroscope/app/ocirepository.yaml (+16 -0)

📄 Description

Pyroscope v2.0 introduced breaking changes to the Helm chart values and storage architecture. This PR performs the migration to Helm chart v2.0.1 with all required value remapping, and removes the Renovate blocking rule that was added in anticipation of this work.

Changes

kubernetes/apps/observability/pyroscope/app/ocirepository.yaml (new) — replaces the HelmRepository with an OCIRepository sourcing oci://ghcr.io/grafana/helm-charts/pyroscope at tag 2.0.1 with a pinned digest (sha256:51859560888c54ca415d43f438d93e1c5f0b9aa2fbedf2e41655df50f692f793), consistent with how other apps in the repo are wired.
kubernetes/apps/observability/pyroscope/app/helmrelease.yaml — switched from chart.spec (HelmRepository reference) to chartRef pointing to the new OCIRepository, and added explicit architecture.storage settings:

architecture:
  storage:
    v1: true
    v2: false

Setting v2: false is required to preserve the existing v1 data/storage path and prevent a startup failure — Pyroscope v2.0 will error at startup if v2 storage is enabled without an object-storage backend configured. All existing values keys (pyroscope.extraArgs, pyroscope.persistence, pyroscope.resources, serviceMonitor) remain valid in v2.0. The removed v1.x keys (persistence.shared, migration.queryBackend, all.enable-v1-write-path) were not in use.

kubernetes/apps/observability/pyroscope/app/helmrepository.yaml (deleted) — no longer needed; replaced by the OCIRepository.
kubernetes/apps/observability/pyroscope/app/kustomization.yaml — updated to reference ocirepository.yaml instead of helmrepository.yaml.
.renovaterc.json5 — removed the temporary packageRule that blocked major-version auto-upgrades for the pyroscope Helm chart.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/webgrip/homelab-cluster/pull/48 **Author:** [@Copilot](https://github.com/apps/copilot-swe-agent) **Created:** 5/19/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `copilot/chore-plan-migration-to-helm-v2-0` --- ### 📝 Commits (4) - [`c67fe38`](https://github.com/webgrip/homelab-cluster/commit/c67fe383f1302dc98c1e2f035aeff4b962dd3d1a) Initial plan - [`edde5b9`](https://github.com/webgrip/homelab-cluster/commit/edde5b90a046e8f07bc41eed742a1fb0e86330d0) chore(renovate): block Pyroscope major version auto-upgrade (v2.0 breaking changes) - [`4af6e3b`](https://github.com/webgrip/homelab-cluster/commit/4af6e3bb92f2d7f65a57aec2b289cc1e65d827db) feat(pyroscope)!: migrate to Helm chart v2.0.1 with v1 storage path preserved - [`305ab39`](https://github.com/webgrip/homelab-cluster/commit/305ab39209ebb7a2610f8379576562c3a8d0531c) chore(pyroscope): switch to OCIRepository with SHA digest pinning ### 📊 Changes **4 files changed** (+26 additions, -20 deletions) <details> <summary>View changed files</summary> 📝 `kubernetes/apps/observability/pyroscope/app/helmrelease.yaml` (+9 -8) ➖ `kubernetes/apps/observability/pyroscope/app/helmrepository.yaml` (+0 -11) 📝 `kubernetes/apps/observability/pyroscope/app/kustomization.yaml` (+1 -1) ➕ `kubernetes/apps/observability/pyroscope/app/ocirepository.yaml` (+16 -0) </details> ### 📄 Description Pyroscope v2.0 introduced breaking changes to the Helm chart values and storage architecture. This PR performs the migration to Helm chart v2.0.1 with all required value remapping, and removes the Renovate blocking rule that was added in anticipation of this work. ## Changes - **`kubernetes/apps/observability/pyroscope/app/ocirepository.yaml`** (new) — replaces the `HelmRepository` with an `OCIRepository` sourcing `oci://ghcr.io/grafana/helm-charts/pyroscope` at tag `2.0.1` with a pinned digest (`sha256:51859560888c54ca415d43f438d93e1c5f0b9aa2fbedf2e41655df50f692f793`), consistent with how other apps in the repo are wired. - **`kubernetes/apps/observability/pyroscope/app/helmrelease.yaml`** — switched from `chart.spec` (HelmRepository reference) to `chartRef` pointing to the new `OCIRepository`, and added explicit `architecture.storage` settings: ```yaml architecture: storage: v1: true v2: false ``` Setting `v2: false` is required to preserve the existing v1 data/storage path and prevent a startup failure — Pyroscope v2.0 will error at startup if v2 storage is enabled without an object-storage backend configured. All existing values keys (`pyroscope.extraArgs`, `pyroscope.persistence`, `pyroscope.resources`, `serviceMonitor`) remain valid in v2.0. The removed v1.x keys (`persistence.shared`, `migration.queryBackend`, `all.enable-v1-write-path`) were not in use. - **`kubernetes/apps/observability/pyroscope/app/helmrepository.yaml`** (deleted) — no longer needed; replaced by the `OCIRepository`. - **`kubernetes/apps/observability/pyroscope/app/kustomization.yaml`** — updated to reference `ocirepository.yaml` instead of `helmrepository.yaml`. - **`.renovaterc.json5`** — removed the temporary packageRule that blocked major-version auto-upgrades for the `pyroscope` Helm chart. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

ryangr0

2026-06-08 08:31:28 +00:00

closed this issue
added the
pull-request
label

No labels

pull-request

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

webgrip/homelab-cluster#313

No description provided.

Rows
Columns