feat(k8s): use Lakekeeper as the Iceberg Catalog in the Kubernetes deployment#4275
Open
mengw15 wants to merge 7 commits into
Open
feat(k8s): use Lakekeeper as the Iceberg Catalog in the Kubernetes deployment#4275mengw15 wants to merge 7 commits into
mengw15 wants to merge 7 commits into
Conversation
mengw15
changed the title
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4275 +/- ##
=========================================
Coverage 43.21% 43.22%
- Complexity 2185 2186 +1
=========================================
Files 1035 1035
Lines 38843 38843
Branches 4061 4061
=========================================
+ Hits 16785 16788 +3
Misses 21006 21006
+ Partials 1052 1049 -3
*This pull request uses carry forward flags. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
xuang7
approved these changes
May 12, 2026
Contributor
xuang7
left a comment
xuang7
left a comment
There was a problem hiding this comment.
LGTM! Tested on local k8s, services work fine. This branch is behind main, please sync before merging.
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
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 adds the Kubernetes / Helm deployment for the Lakekeeper-based Result Service.
Files changed:
bin/k8s/Chart.yaml: added Lakekeeper Helm chart dependency (lakekeeperv0.9.0)bin/k8s/values.yaml: added Lakekeeper andlakekeeperInitconfiguration (warehouse name, S3 bucket, region, defaultproject)
bin/k8s/templates/lakekeeper-init-job.yaml(new): Kubernetes Job that bootstraps Lakekeeper — creates MinIO bucket,default project, and warehouse
bin/k8s/templates/external-names.yaml: added Lakekeeper ExternalName service for computing-unit-pool namespace accessbin/k8s/templates/workflow-computing-unit-manager-deployment.yaml: switched from Postgres catalog to REST catalog envvars; added
wait-lakekeeperinit containerbin/k8s/templates/webserver-deployment.yaml: added REST catalog env varsbin/k8s/templates/postgresql-init-script-config.yaml: added Lakekeeper database initializationbin/k8s/files/texera_lakekeeper.sql(new): symlink tosql/texera_lakekeeper.sqlAny related issues, documentation, discussions?
close #4610
How was this PR tested?
Manually tested
Was this PR authored or co-authored using generative AI tooling?
co-authored with claude