chore(deps): update generic-service docker tag to v5 - #181
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
Helm Template Diff —
|
Helm Template Diff —
|
Helm Template Diff —
|
Helm Template Diff —
|
Helm Template Diff —
|
Helm Template Diff —
|
Helm Template Diff —
|
Helm Template Diff —
|
Helm Template Diff —
|
Helm Template Diff —
|
Helm Template Diff —
|
Helm Template Diff —
|
Owner
Renovate Review:
|
| Check | Result |
|---|---|
| Inputs | Complete — Release Notes present with explicit BREAKING CHANGES; matching diff comment present (03-apps-apps-adguard-home). |
| Description vs. diff | Consistent — 03_apps/apps/adguard-home/app.yaml bumps helm.version 4.6.0→5.0.0 only, matching the table. |
| Rendered diff | Full, no truncation (13 changed lines) — cosmetic label bump (helm.sh/chart) across the adguard-home/adguard-home-dns Service/Deployment resources, plus one behavioral addition: automountServiceAccountToken: false added to the Deployment pod spec. |
| Changelog vs. config | No overlap — this app sets no serviceAccount/automountToken key anywhere (values.yaml/-prod/-test), and adguard-home (a DNS/ad-filtering service) has no apparent need for in-cluster API access. |
Details:
automountServiceAccountToken: falseis the concrete manifestation of the chart's stated breaking change (stop mounting the API token into pods by default) — confirmed via the rendered diff, not just the release notes text.- Repo-wide search for
automountToken/serviceAccountoverrides under this app's files returned nothing, so nothing here was relying on the previous default.
Why MEDIUM: Major version bump whose breaking change is visibly present in the render, but it's a security-hardening default with no live override or plausible API-access need for this app — contained blast radius, not escalated to High.
Generated by Claude Code
Owner
Renovate Review:
|
| Check | Result |
|---|---|
| Inputs | Complete — Release Notes present with explicit BREAKING CHANGES; matching diff comment present (03-apps-apps-adguard-sync). |
| Description vs. diff | Consistent — 03_apps/apps/adguard-sync/app.yaml bumps helm.version 4.6.0→5.0.0 only, matching the table. |
| Rendered diff | Full, no truncation (11 changed lines) — cosmetic label bump (helm.sh/chart), plus automountServiceAccountToken: false added to the Deployment pod spec. |
| Changelog vs. config | No overlap — this app sets no serviceAccount/automountToken key; adguard-sync (ghcr.io/bakito/adguardhome-sync) syncs config between AdGuard instances over HTTP, no in-cluster K8s API usage apparent. |
Details:
automountServiceAccountToken: falseis the concrete manifestation of the chart's stated breaking change, confirmed via the rendered diff.- No
automountToken/serviceAccountoverride exists anywhere for this app.
Why MEDIUM: Major version bump whose breaking change is visibly present in the render, but it's a security-hardening default with no live override or plausible API-access need for this app — contained blast radius, not escalated to High.
Generated by Claude Code
Owner
Renovate Review:
|
| Check | Result |
|---|---|
| Inputs | Complete — Release Notes present with explicit BREAKING CHANGES; matching diff comment present (03-apps-apps-cloudnative-pg-pgadmin). |
| Description vs. diff | Consistent — 03_apps/apps/cloudnative-pg/pgadmin-app.yaml bumps helm.version 4.6.0→5.0.0 only, matching the table. |
| Rendered diff | Full, no truncation (11 changed lines) — cosmetic label bump (helm.sh/chart), plus automountServiceAccountToken: false added to the Deployment pod spec. |
| Changelog vs. config | No overlap — pgadmin-values.yaml/-prod/-test set no serviceAccount/automountToken key; pgadmin (dpage/pgadmin4) is a DB admin UI with no in-cluster K8s API usage. |
Details:
automountServiceAccountToken: falseis the concrete manifestation of the chart's stated breaking change, confirmed via the rendered diff.- No
automountToken/serviceAccountoverride exists for pgadmin in any of its value files.
Why MEDIUM: Major version bump whose breaking change is visibly present in the render, but it's a security-hardening default with no live override or plausible API-access need for this app — contained blast radius, not escalated to High.
Generated by Claude Code
Owner
Renovate Review:
|
| Check | Result |
|---|---|
| Inputs | Complete — Release Notes present with explicit BREAKING CHANGES; matching diff comment present (03-apps-apps-crowdsec-web-ui). |
| Description vs. diff | Consistent — 03_apps/apps/crowdsec/web-ui-app.yaml bumps helm.version 4.6.0→5.0.0 only, matching the table. |
| Rendered diff | Full, no truncation (11 changed lines) — cosmetic label bump (helm.sh/chart), plus automountServiceAccountToken: false added to the Deployment pod spec. |
| Changelog vs. config | No overlap — no serviceAccount/automountToken override for this app; crowdsec-web-ui (ghcr.io/theduffman85/crowdsec-web-ui) is a read-only dashboard for CrowdSec, no in-cluster K8s API usage apparent. |
Details:
automountServiceAccountToken: falseis the concrete manifestation of the chart's stated breaking change, confirmed via the rendered diff.- No
automountToken/serviceAccountoverride exists for this app.
Why MEDIUM: Major version bump whose breaking change is visibly present in the render, but it's a security-hardening default with no live override or plausible API-access need for this app — contained blast radius, not escalated to High.
Generated by Claude Code
Owner
Renovate Review:
|
| Check | Result |
|---|---|
| Inputs | Complete — Release Notes present with explicit BREAKING CHANGES; matching diff comment present (03-apps-apps-demo-podinfo). |
| Description vs. diff | Consistent — 03_apps/apps/demo-podinfo/app.yaml bumps helm.version 4.6.0→5.0.0 only, matching the table. |
| Rendered diff | Full, no truncation (11 changed lines) — cosmetic label bump (helm.sh/chart), plus automountServiceAccountToken: false added to the Deployment pod spec. |
| Changelog vs. config | No overlap — no serviceAccount/automountToken override for this app; demo-podinfo (ghcr.io/stefanprodan/podinfo) is a demo/test workload with no in-cluster K8s API usage. |
Details:
automountServiceAccountToken: falseis the concrete manifestation of the chart's stated breaking change, confirmed via the rendered diff.- No
automountToken/serviceAccountoverride exists for this app.
Why MEDIUM: Major version bump whose breaking change is visibly present in the render, but it's a security-hardening default with no live override or plausible API-access need for this app — contained blast radius, not escalated to High.
Generated by Claude Code
Owner
Renovate Review:
|
| Check | Result |
|---|---|
| Inputs | Complete — Release Notes present with explicit BREAKING CHANGES; matching diff comment present (03-apps-apps-heimdall). |
| Description vs. diff | Consistent — 03_apps/apps/heimdall/app.yaml bumps helm.version 4.6.0→5.0.0 only, matching the table. |
| Rendered diff | Full, no truncation (11 changed lines) — cosmetic label bump (helm.sh/chart), plus automountServiceAccountToken: false added to the Deployment pod spec. |
| Changelog vs. config | No overlap — no serviceAccount/automountToken override for this app; heimdall (lscr.io/linuxserver/heimdall) is a dashboard/link launcher with no in-cluster K8s API usage. |
Details:
automountServiceAccountToken: falseis the concrete manifestation of the chart's stated breaking change, confirmed via the rendered diff.- No
automountToken/serviceAccountoverride exists for this app. (Unrelated to this PR: the pod spec already runsrunAsUser: 0, pre-existing and untouched by this bump — noted only for completeness, not a finding of this review.)
Why MEDIUM: Major version bump whose breaking change is visibly present in the render, but it's a security-hardening default with no live override or plausible API-access need for this app — contained blast radius, not escalated to High.
Generated by Claude Code
Owner
Renovate Review:
|
| Check | Result |
|---|---|
| Inputs | Complete — Release Notes present with explicit BREAKING CHANGES; matching diff comment present (03-apps-apps-home-assistant). |
| Description vs. diff | Consistent — 03_apps/apps/home-assistant/app.yaml bumps helm.version 4.6.0→5.0.0 only, matching the table. |
| Rendered diff | Full, no truncation (11 changed lines) — cosmetic label bump (helm.sh/chart), plus automountServiceAccountToken: false added to the Deployment pod spec. |
| Changelog vs. config | No overlap — no serviceAccount/automountToken override for this app; home-assistant integrates with local network devices/services, no in-cluster K8s API usage apparent from its config. |
Details:
automountServiceAccountToken: falseis the concrete manifestation of the chart's stated breaking change, confirmed via the rendered diff.- No
automountToken/serviceAccountoverride exists for this app. (Unrelated to this PR: the pod spec setsrunAsNonRoot: false, pre-existing and untouched by this bump — noted only for completeness.)
Why MEDIUM: Major version bump whose breaking change is visibly present in the render, but it's a security-hardening default with no live override or plausible API-access need for this app — contained blast radius, not escalated to High.
Generated by Claude Code
Owner
Renovate Review:
|
| Check | Result |
|---|---|
| Inputs | Complete — Release Notes present with explicit BREAKING CHANGES; matching diff comment present (03-apps-apps-jellyfin). |
| Description vs. diff | Consistent — 03_apps/apps/jellyfin/app.yaml bumps helm.version 4.6.0→5.0.0 only, matching the table. |
| Rendered diff | Full, no truncation (11 changed lines) — cosmetic label bump (helm.sh/chart), plus automountServiceAccountToken: false added to the Deployment pod spec. |
| Changelog vs. config | No overlap — no serviceAccount/automountToken override for this app; jellyfin (ghcr.io/jellyfin/jellyfin) is a media server with no in-cluster K8s API usage. |
Details:
automountServiceAccountToken: falseis the concrete manifestation of the chart's stated breaking change, confirmed via the rendered diff.- No
automountToken/serviceAccountoverride exists for this app.
Why MEDIUM: Major version bump whose breaking change is visibly present in the render, but it's a security-hardening default with no live override or plausible API-access need for this app — contained blast radius, not escalated to High.
Generated by Claude Code
Owner
Renovate Review:
|
| Check | Result |
|---|---|
| Inputs | Complete — Release Notes present with explicit BREAKING CHANGES; matching diff comment present (03-apps-apps-mosquitto). |
| Description vs. diff | Consistent — 03_apps/apps/mosquitto/app.yaml bumps helm.version 4.6.0→5.0.0 only, matching the table. |
| Rendered diff | Full, no truncation (11 changed lines) — cosmetic label bump (helm.sh/chart), plus automountServiceAccountToken: false added to the Deployment pod spec. |
| Changelog vs. config | No overlap — no serviceAccount/automountToken override for this app; mosquitto (eclipse-mosquitto) is an MQTT broker with no in-cluster K8s API usage. |
Details:
automountServiceAccountToken: falseis the concrete manifestation of the chart's stated breaking change, confirmed via the rendered diff.- No
automountToken/serviceAccountoverride exists for this app.
Why MEDIUM: Major version bump whose breaking change is visibly present in the render, but it's a security-hardening default with no live override or plausible API-access need for this app — contained blast radius, not escalated to High.
Generated by Claude Code
Owner
Renovate Review:
|
| Check | Result |
|---|---|
| Inputs | Complete — Release Notes present with explicit BREAKING CHANGES; matching diff comment present (03-apps-apps-n8n). |
| Description vs. diff | Consistent — 03_apps/apps/n8n/app.yaml bumps helm.version 4.6.0→5.0.0 only, matching the table. |
| Rendered diff | Full, no truncation (11 changed lines) — cosmetic label bump (helm.sh/chart), plus automountServiceAccountToken: false added to the Deployment pod spec. |
| Changelog vs. config | No overlap — no serviceAccount/automountToken override for this app; n8n (docker.n8n.io/n8nio/n8n) is a workflow-automation tool, no in-cluster K8s API usage apparent from its config here (it may call external/internal HTTP services per user-defined workflows, but that's unrelated to the ServiceAccount token). |
Details:
automountServiceAccountToken: falseis the concrete manifestation of the chart's stated breaking change, confirmed via the rendered diff.- No
automountToken/serviceAccountoverride exists for this app.
Why MEDIUM: Major version bump whose breaking change is visibly present in the render, but it's a security-hardening default with no live override or plausible API-access need for this app — contained blast radius, not escalated to High.
Generated by Claude Code
Owner
Renovate Review:
|
| Check | Result |
|---|---|
| Inputs | Complete — Release Notes present with explicit BREAKING CHANGES; matching diff comment present (03-apps-apps-nodered). |
| Description vs. diff | Consistent — unlike the other 11 apps here, nodered consumes this chart as an aliased Helm dependency in 03_apps/apps/nodered/Chart.yaml (name: generic-service, alias: nodered, version 4.6.0→5.0.0), which is why its rendered resources carry helm.sh/chart: nodered-* labels instead of generic-service-*. Version bump matches the table. |
| Rendered diff | Full, no truncation (9 changed lines) — cosmetic label bump (helm.sh/chart: nodered-4.6.0→nodered-5.0.0) across nodered/nodered-integration resources, plus automountServiceAccountToken: false added to the Deployment pod spec. |
| Changelog vs. config | No overlap — no serviceAccount/automountToken override for this app; nodered (nodered/node-red) is a flow-automation tool, has a custom.network/postgresdb: egress network label for DB access but nothing indicating in-cluster K8s API usage. |
Details:
automountServiceAccountToken: falseis the concrete manifestation of the chart's stated breaking change, confirmed via the rendered diff.- No
automountToken/serviceAccountoverride exists for this app.
Why MEDIUM: Major version bump whose breaking change is visibly present in the render, but it's a security-hardening default with no live override or plausible API-access need for this app — contained blast radius, not escalated to High.
Generated by Claude Code
Owner
Renovate Review:
|
| Check | Result |
|---|---|
| Inputs | Complete — Release Notes present with explicit BREAKING CHANGES; matching diff comment present (03-apps-apps-teamspeak). |
| Description vs. diff | Consistent — 03_apps/apps/teamspeak/app.yaml bumps helm.version 4.6.0→5.0.0 only, matching the table. |
| Rendered diff | Full, no truncation (13 changed lines) — cosmetic label bump (helm.sh/chart) across teamspeak/teamspeak-admin resources, plus automountServiceAccountToken: false added to the Deployment pod spec. |
| Changelog vs. config | No overlap — no serviceAccount/automountToken override for this app; teamspeak (docker.io/teamspeak) is a voice-chat server with no in-cluster K8s API usage. |
Details:
automountServiceAccountToken: falseis the concrete manifestation of the chart's stated breaking change, confirmed via the rendered diff.- No
automountToken/serviceAccountoverride exists for this app.
Why MEDIUM: Major version bump whose breaking change is visibly present in the render, but it's a security-hardening default with no live override or plausible API-access need for this app — contained blast radius, not escalated to High.
Generated by Claude Code
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.
This PR contains the following updates:
4.6.0→5.0.0Release Notes
lunarys/generic-helm-chart (generic-service)
v5.0.0Compare Source
Features
BREAKING CHANGES
serviceAccount.automountToken is set to true. Workloads using an
in-cluster Kubernetes client, or sidecars injected by a mutating webhook
that needs the token, must opt in.
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.