bobbai00 opened a new pull request, #4072:
URL: https://github.com/apache/texera/pull/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)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to