q792602257/DataMate
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[Feature] Refactor project to use 'datamate' naming convention for services and configurations (#14)

Browse Source 
* Enhance CleaningTaskService to track cleaning process progress and update ExecutorType to DATAMATE

* Refactor project to use 'datamate' naming convention for services and configurations
This commit is contained in:
hhhhsc701
2025-10-22 17:53:16 +08:00
committed by GitHub
parent 175d9ded93
commit 31ef8bc265
39 changed files with 312 additions and 737 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
deployment/helm/ray/kuberay-operator/values.yaml
View File

@@ -3,13 +3,13 @@
# Declare variables to be passed into your templates.
# -- String to partially override release name.
nameOverride: kuberay-operator
nameOverride: datamate-kuberay-operator
# -- String to fully override release name.
fullnameOverride: kuberay-operator
fullnameOverride: datamate-kuberay-operator
# -- String to override component name.
componentOverride: kuberay-operator
componentOverride: datamate-kuberay-operator
image:
# -- Image repository.
@@ -32,7 +32,7 @@ serviceAccount:
create: true
# -- The name of the service account to use.
# If not set and create is true, a name is generated using the fullname template.
name: kuberay-operator
name: datamate-kuberay-operator
logging:
# -- Log encoder to use for stdout (one of `json` or `console`).
@@ -88,7 +88,7 @@ featureGates:
# Configurations for KubeRay operator metrics.
metrics:
# -- Whether KubeRay operator should emit control plane metrics.
enabled: true
enabled: false
serviceMonitor:
# -- Enable a prometheus ServiceMonitor
enabled: false