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

jiadongb pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/texera.git


The following commit(s) were added to refs/heads/main by this push:
     new 188de63827 chore: update Kubernetes Helm chart image references to 
Apache registry (#4072)
188de63827 is described below

commit 188de638279a2e028166a8050ff4839472926917
Author: Jiadong Bai <[email protected]>
AuthorDate: Wed Nov 26 11:30:30 2025 -0800

    chore: update Kubernetes Helm chart image references to Apache registry 
(#4072)
    
    ### What changes were proposed in this PR?
    
    This PR updates all Texera service images in the Kubernetes Helm chart
    (`bin/k8s/values.yaml`) to use the Apache registry with `latest` tags,
    aligning with the naming convention established in the CI/CD workflow
    (#4055).
    
    The following image references have been updated:
    - `texera/texera-example-data-loader:cluster` →
    `apache/texera-example-data-loader:latest`
    - `texera/texera-web-application:cluster` →
    `apache/texera-dashboard-service:latest`
    - `texera/workflow-computing-unit-managing-service:cluster` →
    `apache/texera-workflow-computing-unit-managing-service:latest`
    - `texera/workflow-compiling-service:cluster` →
    `apache/texera-workflow-compiling-service:latest`
    - `texera/file-service:cluster` → `apache/texera-file-service:latest`
    - `texera/config-service:cluster` →
    `apache/texera-config-service:latest`
    - `texera/access-control-service:cluster` →
    `apache/texera-access-control-service:latest`
    - `texera/computing-unit-master:cluster` →
    `apache/texera-workflow-execution-coordinator:latest`
    
    This ensures that the Kubernetes Helm chart uses the correct image names
    and registry that are now being built and pushed by the GitHub Actions
    workflow.
    
    ### Any related issues, documentation, discussions?
    
    Related to #4055 which introduced the GitHub Actions workflow for
    building and pushing images to the Apache registry.
    
    ### How was this PR tested?
    
    This PR only updates image references in the Kubernetes Helm chart
    configuration file. No code changes were made.
    
    ### Was this PR authored or co-authored using generative AI tooling?
    
    Generated-by: Claude (Anthropic)
    
    ---------
    
    Co-authored-by: Claude <[email protected]>
    Co-authored-by: Chen Li <[email protected]>
---
 bin/k8s/values.yaml | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/bin/k8s/values.yaml b/bin/k8s/values.yaml
index 95810913eb..f13fcb4a8c 100644
--- a/bin/k8s/values.yaml
+++ b/bin/k8s/values.yaml
@@ -113,7 +113,7 @@ texeraImages:
 # Example data loader configuration
 exampleDataLoader:
   enabled: true
-  image: texera/texera-example-data-loader:cluster
+  image: apache/texera-example-data-loader:latest
   username: texera
   password: texera
   datasetDir: datasets
@@ -122,7 +122,7 @@ exampleDataLoader:
 webserver:
   name: webserver
   numOfPods: 1  # Number of pods for the Texera deployment
-  imageName: texera/texera-web-application:cluster # image name of the texera
+  imageName: apache/texera-dashboard-service:latest # image name of the texera
   service:
     type: ClusterIP
     port: 8080
@@ -131,7 +131,7 @@ workflowComputingUnitManager:
   name: workflow-computing-unit-manager
   numOfPods: 1
   serviceAccountName: workflow-computing-unit-manager-service-account
-  imageName: texera/workflow-computing-unit-managing-service:cluster
+  imageName: apache/texera-workflow-computing-unit-managing-service:latest
   service:
     type: ClusterIP
     port: 8888
@@ -139,7 +139,7 @@ workflowComputingUnitManager:
 workflowCompilingService:
   name: workflow-compiling-service
   numOfPods: 1
-  imageName: texera/workflow-compiling-service:cluster
+  imageName: apache/texera-workflow-compiling-service:latest
   service:
     type: ClusterIP
     port: 9090
@@ -147,7 +147,7 @@ workflowCompilingService:
 fileService:
   name: file-service
   numOfPods: 1
-  imageName: texera/file-service:cluster
+  imageName: apache/texera-file-service:latest
   service:
     type: ClusterIP
     port: 9092
@@ -155,7 +155,7 @@ fileService:
 configService:
   name: config-service
   numOfPods: 1
-  imageName: texera/config-service:cluster
+  imageName: apache/texera-config-service:latest
   service:
     type: ClusterIP
     port: 9094
@@ -163,7 +163,7 @@ configService:
 accessControlService:
   name: access-control-service
   numOfPods: 1
-  imageName: texera/access-control-service:cluster
+  imageName: apache/texera-access-control-service:latest
   service:
     type: ClusterIP
     port: 9096
@@ -193,7 +193,7 @@ workflowComputingUnitPool:
     cpu: 100
     memory: 100Gi
     nvidiaGpu: 5
-  imageName: texera/computing-unit-master:cluster
+  imageName: apache/texera-workflow-execution-coordinator:latest
   service:
     port: 8085
     targetPort: 8085

Reply via email to