chore: update Kubernetes Helm chart image references to Apache registry #4072
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Update all Texera service images in docker-compose.yml to use the Apache registry with latest tags, following the naming convention established in the CI/CD workflow: - file-service → apache/texera-file-service:latest - workflow-compiling-service → apache/texera-workflow-compiling-service:latest - computing-unit-master → apache/texera-workflow-execution-coordinator:latest - texera-web-application → apache/texera-dashboard-service:latest - texera-example-data-loader → apache/texera-example-data-loader:latest This aligns with the GitHub Actions workflow that builds and pushes images to the Apache registry.
Update all Texera service images in values.yaml to use the Apache registry with latest tags, aligning with the naming convention established in the CI/CD workflow: - texera-example-data-loader:cluster → apache/texera-example-data-loader:latest - texera-web-application:cluster → apache/texera-dashboard-service:latest - workflow-computing-unit-managing-service:cluster → apache/texera-workflow-computing-unit-managing-service:latest - workflow-compiling-service:cluster → apache/texera-workflow-compiling-service:latest - file-service:cluster → apache/texera-file-service:latest - config-service:cluster → apache/texera-config-service:latest - access-control-service:cluster → apache/texera-access-control-service:latest - computing-unit-master:cluster → apache/texera-workflow-execution-coordinator:latest This ensures the Kubernetes Helm chart uses the correct image names and registry that are now being built and pushed by the GitHub Actions workflow.
aicam
reviewed
Nov 24, 2025
Contributor
aicam
left a comment
aicam
left a comment
There was a problem hiding this comment.
I believe we need nightly tag not latest
Contributor
Author
Using latest is a more common practice |
Contributor
|
@aicam If you think this PR is ready, please do the merge. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 withlatesttags, 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:latesttexera/texera-web-application:cluster→apache/texera-dashboard-service:latesttexera/workflow-computing-unit-managing-service:cluster→apache/texera-workflow-computing-unit-managing-service:latesttexera/workflow-compiling-service:cluster→apache/texera-workflow-compiling-service:latesttexera/file-service:cluster→apache/texera-file-service:latesttexera/config-service:cluster→apache/texera-config-service:latesttexera/access-control-service:cluster→apache/texera-access-control-service:latesttexera/computing-unit-master:cluster→apache/texera-workflow-execution-coordinator:latestThis 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)