From d87c4e0e1b9176bc9c5e59128a09a3eef77b6128 Mon Sep 17 00:00:00 2001 From: Pratapa Lakshmi Date: Mon, 7 Sep 2026 15:10:03 +0530 Subject: [PATCH] fix(plane-enterprise): bump iframely v1.2.0 -> v2.5.4 The chart's iframely default was still v1.2.0 (Aug 2025) while every docker-compose target in plane-ee had moved to the v2.5.x line during the v3.0.0 release. That release's audit was scoped to compose only -- the docs/release-v3.0.0-audit notes cover "cli/coolify/portainer commercial, podman compose + quadlets, and the aio Dockerfile build stage" and never mention helm -- so the chart was simply missed rather than deliberately held back. It matters because v1.2.0 is heavily out of date. Trivy, HIGH/CRITICAL with --ignore-unfixed, on linux/amd64: makeplane/iframely:v1.2.0 147 findings, 7 CRITICAL makeplane/iframely:v2.5.4 21 findings, 1 CRITICAL Bumped in all four places the version is spelled out, so `helm show values`, the Rancher questions form, the template fallback and the README table cannot drift apart: - values.yaml services.iframely.image - questions.yml services.iframely.image default - templates/workloads/iframely.deployment.yaml default fallback - README.md values table Safe for the chart's invocation, which is the thing worth checking: the chart sets command=[node] args=[server.js], overriding the image's entrypoint (`exec node cluster.js`), so a restructured image would break it silently. Both tags carry an identical /iframely/server.js (885 bytes) with WorkingDir /iframely and the same entrypoint, so the override still resolves. Note the chart therefore runs iframely single-process rather than clustered -- pre-existing, unchanged here. Verified: `helm lint` passes; `helm template` with the service enabled renders `image: makeplane/iframely:v2.5.4`, and an explicit services.iframely.image override still wins. Chart version 3.5.7 -> 3.5.8, matching how the recent chart fixes (#298, #299, #295) each carried their own patch bump. Co-Authored-By: Claude Opus 5 (1M context) --- charts/plane-enterprise/Chart.yaml | 2 +- charts/plane-enterprise/README.md | 2 +- charts/plane-enterprise/questions.yml | 2 +- .../templates/workloads/iframely.deployment.yaml | 2 +- charts/plane-enterprise/values.yaml | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/charts/plane-enterprise/Chart.yaml b/charts/plane-enterprise/Chart.yaml index c9227e8..5db1386 100644 --- a/charts/plane-enterprise/Chart.yaml +++ b/charts/plane-enterprise/Chart.yaml @@ -5,7 +5,7 @@ description: Meet Plane. An Enterprise software development tool to manage issue type: application -version: 3.5.7 +version: 3.5.8 appVersion: "3.1.4" home: https://plane.so/ diff --git a/charts/plane-enterprise/README.md b/charts/plane-enterprise/README.md index 5e706db..a2a9bd5 100644 --- a/charts/plane-enterprise/README.md +++ b/charts/plane-enterprise/README.md @@ -1297,7 +1297,7 @@ Note: When the email service is enabled, the cert-issuer will be automatically c | services.iframely.cpuLimit | 1000m | | CPU limit for the Iframely service deployment | | services.iframely.memoryRequest | 256Mi | | Memory request for the Iframely service deployment | | services.iframely.cpuRequest | 100m | | CPU request for the Iframely service deployment | -| services.iframely.image | makeplane/iframely:v1.2.0 | | Docker image for the Iframely service deployment | +| services.iframely.image | makeplane/iframely:v2.5.4 | | Docker image for the Iframely service deployment | | services.iframely.pullPolicy | Always | | Image pull policy for the Iframely service deployment | | services.iframely.assign_cluster_ip | false | | Set it to `true` if you want to assign `ClusterIP` to the service | | services.iframely.nodeSelector | {} | | This key allows you to set the node selector for the deployment of `iframely`. This is useful when you want to run the deployment on specific nodes in your Kubernetes cluster. | diff --git a/charts/plane-enterprise/questions.yml b/charts/plane-enterprise/questions.yml index 18e42cd..e272675 100644 --- a/charts/plane-enterprise/questions.yml +++ b/charts/plane-enterprise/questions.yml @@ -1055,7 +1055,7 @@ questions: - variable: services.iframely.image label: "Docker Image" type: string - default: "makeplane/iframely:v1.2.0" + default: "makeplane/iframely:v2.5.4" - variable: services.iframely.pullPolicy label: "Iframely Pull Policy" type: enum diff --git a/charts/plane-enterprise/templates/workloads/iframely.deployment.yaml b/charts/plane-enterprise/templates/workloads/iframely.deployment.yaml index df7d33f..d48debf 100644 --- a/charts/plane-enterprise/templates/workloads/iframely.deployment.yaml +++ b/charts/plane-enterprise/templates/workloads/iframely.deployment.yaml @@ -45,7 +45,7 @@ spec: - name: {{ .Release.Name }}-iframely {{- include "plane.containerSecurityContext" . }} imagePullPolicy: Always - image: {{ .Values.services.iframely.image | default "makeplane/iframely:v1.2.0" }} + image: {{ .Values.services.iframely.image | default "makeplane/iframely:v2.5.4" }} stdin: true tty: true resources: diff --git a/charts/plane-enterprise/values.yaml b/charts/plane-enterprise/values.yaml index b560b8b..a8be378 100644 --- a/charts/plane-enterprise/values.yaml +++ b/charts/plane-enterprise/values.yaml @@ -321,7 +321,7 @@ services: cpuLimit: 1000m memoryRequest: 256Mi cpuRequest: 100m - image: makeplane/iframely:v1.2.0 + image: makeplane/iframely:v2.5.4 pullPolicy: Always assign_cluster_ip: false nodeSelector: {}