makeplane / makeplane/plane

[bug]: env.api_key_rate_limit does not override the default API rate limit from Helm values

Open
#9,034 2 comments 2 reactions 1 assignee View on GitHub

@pratapalakshmi is already working on this.

Since May 11, 2026.

🐛bug plane
Dominant language
TypeScript
Stars
59.6k
Forks
5.8k
Avg merge
1d 22h
Merged PRs (30d)
49

Description

Is there an existing issue for this?
  • I have searched the existing issues
Current behavior

The API rate limit works with the default configuration.

However, when setting a custom value through values.yaml, the value does not appear to override the effective API rate limit.

Example:

env:
  api_key_rate_limit: "60/second"

After rendering the Helm chart, the value is present in the application ConfigMap as:

API_KEY_RATE_LIMIT: "60/second"

The API deployment imports this ConfigMap through envFrom, so the environment variable is available inside the container.

Even so, the effective API rate limit still appears to remain at the default value.

The custom rate limit only worked after explicitly adding DEFAULT_API_RATE_LIMIT through extraEnv:

env:
  api_key_rate_limit: &api_rate_limit "60/second"

extraEnv:
  - name: DEFAULT_API_RATE_LIMIT
    value: *api_rate_limit

After adding this workaround, the custom rate limit was applied correctly.

Steps to reproduce
  1. Deploy Plane using the Helm chart.

  2. Set a custom API rate limit in values.yaml:

env:
  api_key_rate_limit: "60/second"
  1. Apply the Helm release:
helm upgrade --install plane-app <chart-name> \
  --namespace plane \
  -f values.yaml
  1. Check the rendered manifest or ConfigMap:
helm get manifest plane-app -n plane | grep -A 5 API_KEY_RATE_LIMIT

Expected rendered value:

API_KEY_RATE_LIMIT: "60/second"
  1. Restart the API deployment:
kubectl rollout restart deployment/plane-app-api-wl -n plane
  1. Test the effective API rate limit.

  2. Notice that the configured value does not appear to override the default rate limit.

  3. Add the workaround:

env:
  api_key_rate_limit: &api_rate_limit "60/second"

extraEnv:
  - name: DEFAULT_API_RATE_LIMIT
    value: *api_rate_limit
  1. Apply the Helm release again and restart the API deployment.

  2. Test again and confirm that the custom rate limit is now applied correctly.

Environment

Production

Browser

None

Variant

Self-hosted

Version

2.5.4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.