This is an automated email from the ASF dual-hosted git repository.

zihaoxiang pushed a commit to branch dev
in repository https://gitbox.apache.org/repos/asf/dolphinscheduler.git


The following commit(s) were added to refs/heads/dev by this push:
     new 16a9941d44 [Fix-16410] wrong env in values.yaml (#16412)
16a9941d44 is described below

commit 16a9941d44cab1230d1b2c1d24cc7a29e02189b8
Author: Lijing Ye <[email protected]>
AuthorDate: Fri Aug 2 23:35:01 2024 +0800

    [Fix-16410] wrong env in values.yaml (#16412)
---
 deploy/kubernetes/dolphinscheduler/README.md   | 2 +-
 deploy/kubernetes/dolphinscheduler/values.yaml | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/deploy/kubernetes/dolphinscheduler/README.md 
b/deploy/kubernetes/dolphinscheduler/README.md
index 347c07e8de..4a38a5e4d3 100644
--- a/deploy/kubernetes/dolphinscheduler/README.md
+++ b/deploy/kubernetes/dolphinscheduler/README.md
@@ -307,7 +307,6 @@ Please refer to the [Quick Start in 
Kubernetes](../../../docs/docs/en/guide/inst
 | worker.customizedConfig | object | `{}` | configure aligned with 
https://github.com/apache/dolphinscheduler/blob/dev/dolphinscheduler-worker/src/main/resources/application.yaml
 |
 | worker.enableCustomizedConfig | bool | `false` | enable configure custom 
config |
 | worker.enabled | bool | `true` | Enable or disable the Worker component |
-| worker.env.DEFAULT_TENANT_ENABLED | bool | `false` | If set true, will use 
worker bootstrap user as the tenant to execute task when the tenant is 
`default`; |
 | worker.env.WORKER_EXEC_THREADS | string | `"100"` | Worker execute thread 
number to limit task instances |
 | worker.env.WORKER_HOST_WEIGHT | string | `"100"` | Worker host weight to 
dispatch tasks |
 | worker.env.WORKER_MAX_HEARTBEAT_INTERVAL | string | `"10s"` | Worker 
heartbeat interval |
@@ -317,6 +316,7 @@ Please refer to the [Quick Start in 
Kubernetes](../../../docs/docs/en/guide/inst
 | 
worker.env.WORKER_SERVER_LOAD_PROTECTION_MAX_SYSTEM_CPU_USAGE_PERCENTAGE_THRESHOLDS
 | float | `0.7` | Worker max system cpu usage, when the worker's system cpu 
usage is smaller then this value, worker server can be dispatched tasks. |
 | 
worker.env.WORKER_SERVER_LOAD_PROTECTION_MAX_SYSTEM_MEMORY_USAGE_PERCENTAGE_THRESHOLDS
 | float | `0.7` | Worker max memory usage , when the worker's memory usage is 
smaller then this value, worker server can be dispatched tasks. |
 | worker.env.WORKER_TENANT_CONFIG_AUTO_CREATE_TENANT_ENABLED | bool | `true` | 
tenant corresponds to the user of the system, which is used by the worker to 
submit the job. If system does not have this user, it will be automatically 
created after the parameter worker.tenant.auto.create is true. |
+| worker.env.WORKER_TENANT_CONFIG_DEFAULT_TENANT_ENABLED | bool | `false` | If 
set true, will use worker bootstrap user as the tenant to execute task when the 
tenant is `default`; |
 | worker.keda.advanced | object | `{}` | Specify HPA related options |
 | worker.keda.cooldownPeriod | int | `30` | How many seconds KEDA will wait 
before scaling to zero. Note that HPA has a separate cooldown period for 
scale-downs |
 | worker.keda.enabled | bool | `false` | Enable or disable the Keda component |
diff --git a/deploy/kubernetes/dolphinscheduler/values.yaml 
b/deploy/kubernetes/dolphinscheduler/values.yaml
index 377620d21b..41a7dfb9c2 100644
--- a/deploy/kubernetes/dolphinscheduler/values.yaml
+++ b/deploy/kubernetes/dolphinscheduler/values.yaml
@@ -688,7 +688,7 @@ worker:
     # -- tenant corresponds to the user of the system, which is used by the 
worker to submit the job. If system does not have this user, it will be 
automatically created after the parameter worker.tenant.auto.create is true.
     WORKER_TENANT_CONFIG_AUTO_CREATE_TENANT_ENABLED: true
     # -- If set true, will use worker bootstrap user as the tenant to execute 
task when the tenant is `default`;
-    DEFAULT_TENANT_ENABLED: false
+    WORKER_TENANT_CONFIG_DEFAULT_TENANT_ENABLED: false
 
   keda:
     # -- Enable or disable the Keda component

Reply via email to