.gitignore (1)

7-8: Consider explicit directory ignore patterns.

It’s clearer to append a trailing slash (/) to indicate directory exclusion and avoid accidentally ignoring files named charts elsewhere:

-charts/plane-ce/charts
-charts/plane-enterprise/charts
+charts/plane-ce/charts/
+charts/plane-enterprise/charts/

charts/plane-ce/Chart.yaml (1)

18-22: Add newline at end of file.

YAMLlint flags a missing newline at EOF. Please ensure there is exactly one blank line (newline character) at the end to comply with YAML standards.

🧰 Tools

🪛 YAMLlint (1.37.1)

[error] 22-22: no new line character at the end of file

(new-line-at-end-of-file)

charts/plane-enterprise/Chart.yaml (1)

20-20: Add newline at end of file.

YAMLlint reports a missing newline at EOF. Ensure one newline is present at the end.

🧰 Tools

🪛 YAMLlint (1.37.1)

[error] 20-20: no new line character at the end of file

(new-line-at-end-of-file)

charts/plane-ce/values.yaml (1)

169-174: Define memory utilization threshold for autoscaling.

The HPA templates conditionally include a memory metric (targetMemoryUtilizationPercentage), but no default is declared here. To enable memory-based scaling, consider extending the block:

autoscaling:
  enabled: true
  minReplicas: 1
  maxReplicas: 3
  targetCPUUtilizationPercentage: 80
  targetMemoryUtilizationPercentage: 80

charts/plane-ce/templates/workloads/api.deployment.yaml (1)

79-119: Extract HPA templating into a shared helper.

Multiple workloads use identical HPA definitions. To reduce duplication and simplify maintenance, move the HPA spec into a template helper (e.g., _hpa.tpl) and include it with parameters:

{{- define "plane.hpa" -}}
apiVersion: {{ ternary "autoscaling/v2" "autoscaling/v2beta2" ... }}
kind: HorizontalPodAutoscaler
metadata:
  name: {{ .name }}-hpa
  namespace: {{ .namespace }}
spec:
  scaleTargetRef:
    ...
  minReplicas: {{ .minReplicas }}
  maxReplicas: {{ .maxReplicas }}
  metrics:
    {{ include "plane.hpa.metrics" .metrics | indent 2 }}
{{- end }}

Then invoke:

{{- if .Values.autoscaling.enabled }}
{{- include "plane.hpa" (dict "name" .Release.Name "-api" "namespace" .Release.Namespace "minReplicas" .Values.autoscaling.minReplicas "maxReplicas" .Values.autoscaling.maxReplicas "metrics" .Values.autoscaling ) | indent 0 }}
{{- end }}

🧰 Tools

🪛 YAMLlint (1.37.1)

[error] 119-119: no new line character at the end of file

(new-line-at-end-of-file)

charts/plane-ce/templates/workloads/live.deployment.yaml (1)

69-76: DRY: Extract shared HPA definition into a helper
The HPA block is duplicated across multiple workload templates. Consider moving it into a single _hpa.tpl partial and passing in the release name, target deployment, and metrics so you’re not repeating the same code in every file.

charts/plane-ce/templates/workloads/space.deployment.yaml (1)

78-101: DRY up CPU/memory metric blocks
The CPU and memory resource metrics share the same structure with only the name and value differing. Consider looping over a map to eliminate duplication and simplify future extensions:

metrics:
  {{- $m := dict "cpu" .Values.autoscaling.targetCPUUtilizationPercentage "memory" .Values.autoscaling.targetMemoryUtilizationPercentage }}
  {{- range $name, $pct := $m }}
    {{- if $pct }}
  - type: Resource
    resource:
      name: {{ $name }}
    {{- if $.Capabilities.APIVersions.Has "autoscaling/v2" }}
      target:
        type: Utilization
        averageUtilization: {{ $pct }}
    {{- else }}
      targetAverageUtilization: {{ $pct }}
    {{- end }}
    {{- end }}
  {{- end }}

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

charts/plane-ce/values.yaml (6)

93-98: Apply autoscaling refactor to space component

This autoscaling block is a direct duplicate of the one in web (lines 79–85). Apply the same anchor/helper refactor here to avoid repetition.

---

107-112: Apply autoscaling refactor to admin component

Duplicate autoscaling settings detected—reuse the common definition via YAML anchors or a shared Helm template.

---

121-126: Apply autoscaling refactor to live component

Identical block as above; extract into a shared anchor/helper to simplify updates.

---

135-140: Apply autoscaling refactor to api component

Same autoscaling parameters—consider consolidating under a single definition for consistency.

---

148-153: Apply autoscaling refactor to worker component

This block repeats the common autoscaling settings—extract and reference a shared anchor or template.

---

161-166: Apply autoscaling refactor to beatworker component

Again, identical to other components. Leverage a YAML anchor or Helm helper to DRY this configuration.

charts/plane-ce/values.yaml (2)

79-85: Refactor repeated autoscaling blocks and remove trailing whitespace

The autoscaling configuration under web is identical across all service components. To improve maintainability and adhere to DRY, consider defining a YAML anchor (or a Helm helper) for the common autoscaling block and reusing it.
Also, line 83 has trailing spaces after 80—please remove them to satisfy lint rules.

🧰 Tools

🪛 YAMLlint (1.37.1)

[error] 83-83: trailing spaces

(trailing-spaces)

---

211-211: Remove extra blank line at end of file

YAML lint warns about too many blank lines. Please delete the extraneous blank line to comply with the lint rule.

🧰 Tools

🪛 YAMLlint (1.37.1)

[warning] 211-211: too many blank lines

(1 > 0) (empty-lines)

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

.github/workflows/chart-releaser.yml (1)

101-106: Add a dedicated dependency build step for Plane-CE
The new Build Dependencies step correctly invokes helm dependency build charts/${{ env.CHART_NAME_CE }} to pull in the metrics-server chart before releasing.

Recommendation:

• Move the conditional inside the step to a step-level if: so the step is skipped entirely when plane-ce is false.
• Add an id: field for clearer logging and potential downstream references.

Example refactor:

-      - name: Build Dependencies
-        run: |
-          if [ "${{ github.event.inputs.plane-ce }}" = "true" ]; then
-            helm dependency build charts/${{ env.CHART_NAME_CE }}
-          fi
+      - name: Build Plane-CE Dependencies
+        id: build-deps-ce
+        if: ${{ github.event.inputs.plane-ce == 'true' }}
+        run: helm dependency build charts/${{ env.CHART_NAME_CE }}

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

charts/plane-ce/values.yaml (2)

204-204: Fix trailing whitespace and excessive blank lines

There is trailing whitespace on line 82 and excessive blank lines around line 204, as indicated by the static analysis tool.

-    targetCPUUtilizationPercentage: 80  
+    targetCPUUtilizationPercentage: 80

And for line 204, remove the excessive blank line:

  api_key_rate_limit: "60/minute"
-

🧰 Tools

🪛 YAMLlint (1.37.1)

[warning] 204-204: too many blank lines

(1 > 0) (empty-lines)

---

79-159: Document HPA requirements in chart's README

While the implementation correctly checks for the metrics-server's presence, users may not be aware they need the metrics-server installed for autoscaling to work.

Consider adding documentation in the chart's README to inform users that:

1. The chart now supports horizontal pod autoscaling
2. The metrics-server must be installed in the cluster for autoscaling to function
3. How to customize the autoscaling parameters for each component

This will help users understand the new functionality and requirements.

🧰 Tools

🪛 YAMLlint (1.37.1)

[error] 82-82: trailing spaces

(trailing-spaces)

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

charts/plane-ce/values.yaml (2)

82-82: Remove trailing whitespace.
Line 82 has unintended trailing spaces that should be removed to satisfy YAML lint rules.

🧰 Tools

🪛 YAMLlint (1.37.1)

[error] 82-82: trailing spaces

(trailing-spaces)

---

204-204: Remove excessive blank line.
The file ends with an extra blank line; remove it to adhere to the configured empty-lines rule.

🧰 Tools

🪛 YAMLlint (1.37.1)

[warning] 204-204: too many blank lines

(1 > 0) (empty-lines)

charts/plane-enterprise/templates/config-secrets/email-env.yaml (1)

1-22: Cleanup template linting errors
YAMLlint is flagging syntax errors due to Helm directives ({{-) and there’s a trailing space on line 20 and no newline at end-of-file. Consider:

• Removing trailing spaces on line 20.
• Ensuring a final newline.
• Adding a top-of-file comment to disable yamllint for Helm templates.

🧰 Tools

🪛 YAMLlint (1.37.1)

[error] 1-1: syntax error: expected the node content, but found '-'

(syntax)

---

[error] 20-20: trailing spaces

(trailing-spaces)

---

[error] 22-22: no new line character at the end of file

(new-line-at-end-of-file)

charts/plane-enterprise/templates/certs/cert-issuers.yaml (1)

1-1: Suppress YAMLlint false positives and ensure newline
Linter errors on line 1 are false positives due to Helm templating. Add a disable comment for YAMLlint or adjust your linter config, and verify there’s a newline at the end of the file.

🧰 Tools

🪛 YAMLlint (1.37.1)

[error] 1-1: syntax error: expected the node content, but found '-'

(syntax)

charts/plane-enterprise/templates/certs/email-certs.yaml (1)

10-10: Remove trailing spaces and add newline
There’s trailing whitespace on line 10 and no newline at the end of the file (line 15). Please trim the trailing spaces and ensure the file ends with a newline.

Also applies to: 15-15

🧰 Tools

🪛 YAMLlint (1.37.1)

[error] 10-10: trailing spaces

(trailing-spaces)

charts/plane-enterprise/templates/workloads/email.deployment.yaml (4)

1-2: Ensure conditional block syntax and whitespace trimming are correct.

Using {{- if … }} at the top without a trailing - on the end tag may lead to unexpected whitespace or blank lines in the rendered manifest. Consider changing:

- {{- if .Values.services.email_service.enabled }}
+ {{- if .Values.services.email_service.enabled -}}
...
- {{- end }}
+ {{- end -}}

This ensures no extra empty lines appear before or after the block.

🧰 Tools

🪛 YAMLlint (1.37.1)

[error] 1-1: syntax error: expected the node content, but found '-'

(syntax)

---

28-67: Replace exec‐based readinessProbe with tcpSocket.

Relying on nc in the container image may lead to probe failures if netcat isn't installed. A TCP socket probe is more declarative:

 readinessProbe:
-  exec:
-    command:
-    - nc
-    - -zv
-    - localhost
-    - "10025"
+  tcpSocket:
+    port: 10025
   initialDelaySeconds: 30
   periodSeconds: 10
   timeoutSeconds: 5
   failureThreshold: 3

This removes the dependency on nc and is lighter weight.

🧰 Tools

🪛 YAMLlint (1.37.1)

[error] 44-44: trailing spaces

(trailing-spaces)

---

[error] 45-45: trailing spaces

(trailing-spaces)

---

68-74: Remove deprecated serviceAccount field.

In Pod specs, only serviceAccountName is needed; serviceAccount is deprecated since Kubernetes v1.8. You can safely remove:

-      serviceAccount: {{ .Release.Name }}-srv-account

and retain:

      serviceAccountName: {{ .Release.Name }}-srv-account

---

75-88: Fix indentation for envFrom and volumes.

YAML lint warns about inconsistent indentation. For example, envFrom: should be indented 8 spaces from the root of the document, not 10. Align these blocks with your chart’s conventions:

-        envFrom:
-          - configMapRef:
+        envFrom:
+          - configMapRef:
             name: {{ .Release.Name }}-email-vars
             optional: false
...
-      volumes:
-        - name: spam-blacklist
+      volumes:
+        - name: spam-blacklist
           configMap:
             name: {{ .Release.Name }}-email-vars

🧰 Tools

🪛 YAMLlint (1.37.1)

[warning] 75-75: wrong indentation: expected 8 but found 10

(indentation)

---

[warning] 79-79: wrong indentation: expected 8 but found 10

(indentation)

---

[warning] 88-88: wrong indentation: expected 6 but found 8

(indentation)

charts/plane-enterprise/questions.yml (1)

20-24: Quote version strings to avoid YAML parsing quirks.

Unquoted v1.10.0 could be misinterpreted by some parsers. Wrap it in quotes:

-  default: v1.10.0
+  default: "v1.10.0"

This ensures it’s always treated as a string.

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

charts/plane-ce/Chart.yaml (1)

19-22: Add newline at end-of-file

YAML parsers and linters expect a terminating newline. Please ensure there's a blank line after the last dependency entry.

Example diff:

 dependencies:
   - name: metrics-server
     version: 3.12.2
     repository: https://kubernetes-sigs.github.io/metrics-server/
+

🧰 Tools

🪛 YAMLlint (1.37.1)

[error] 22-22: no new line character at the end of file

(new-line-at-end-of-file)

.github/workflows/chart-preview.yml (1)

95-95: Remove trailing whitespace

Line 95 contains trailing spaces, causing a YAML lint error. Please delete any extra spaces on blank lines.

🧰 Tools

🪛 YAMLlint (1.37.1)

[error] 95-95: trailing spaces

(trailing-spaces)

charts/plane-ce/values.yaml (3)

83-83: Remove trailing spaces

The value line for targetCPUUtilizationPercentage: 80 has trailing spaces that trigger a YAML lint warning. Please trim the extra spaces.

🧰 Tools

🪛 YAMLlint (1.37.1)

[error] 83-83: trailing spaces

(trailing-spaces)

---

211-211: Remove extra blank line at EOF

There is an unnecessary blank line after the last value, which violates the linter rule on empty lines. Please remove it.

🧰 Tools

🪛 YAMLlint (1.37.1)

[warning] 211-211: too many blank lines

(1 > 0) (empty-lines)

---

79-85: DRY repeated autoscaling blocks with YAML anchors

The autoscaling configuration for each component is identical. To improve maintainability, consider declaring an anchor for the defaults and reusing it:

autoscalingDefaults: &autoscalingDefaults
  enabled: true
  minReplicas: 1
  maxReplicas: 3
  targetCPUUtilizationPercentage: 80
  targetMemoryUtilizationPercentage: 70

web:
  # ...
  autoscaling:
    <<: *autoscalingDefaults
# repeat for other components...

This reduces duplication and simplifies future changes.

Also applies to: 93-99, 107-113, 121-127, 135-141, 148-154, 161-167

🧰 Tools

🪛 YAMLlint (1.37.1)

[error] 83-83: trailing spaces

(trailing-spaces)

charts/plane-ce/questions.yml (2)

58-81: Remove trailing whitespace from autoscaling entries

Several lines in the new autoscaling question blocks include trailing spaces, leading to YAML lint errors. Please strip trailing whitespace from all these lines.

Also applies to: 113-136, 168-191, 236-259, 313-336, 351-374, 389-412

---

58-81: Consolidate repeated autoscaling questions using YAML anchors

The autoscaling variables are repeated verbatim across multiple components. You can introduce a YAML anchor to define the set once and reference it for each component:

autoscalingBase: &autoscalingBase
  - variable: AUTOSCALING.enabled
    label: "Enable Autoscaling"
    type: boolean
    default: true
  # ... other anchors for min/max/targets

questions:
  - <<: *autoscalingBase
    variable: web.autoscaling.enabled
  # ...

This DRY approach will make updates across all components much easier.

Also applies to: 113-136, 168-191, 236-259, 313-336, 351-374, 389-412

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro