Skip to content

chore: Reduce Texera k8 Resources for Development#4165

Open
Ma77Ball wants to merge 8 commits intoapache:mainfrom
Ma77Ball:Ball-Development-ReduceTexeraK8MemoryUsage
Open

chore: Reduce Texera k8 Resources for Development#4165
Ma77Ball wants to merge 8 commits intoapache:mainfrom
Ma77Ball:Ball-Development-ReduceTexeraK8MemoryUsage

Conversation

@Ma77Ball
Copy link
Contributor

@Ma77Ball Ma77Ball commented Jan 20, 2026

What changes were proposed in this PR?

Added Kubernetes resource requests and limits for all Texera microservices and dependencies in values-development.yaml to support running Texera on resource-constrained hardware (e.g., local k3s clusters, Minikube, or small cloud VMs).

Specifically:

  • PostgreSQL: Reduced CPU request from 1 to 0.25 and memory from 1Gi to 256Mi, with explicit limits.
  • MinIO: Added memory request and limit of 256Mi.
  • Texera microservices (webserver, workflow-computing-unit-manager, workflow-compiling-service, file-service, config-service, access-control-service): Added resource requests (10m CPU, 256Mi memory) and limits (1000m CPU, 256Mi1Gi memory depending on service).

This prevents pods from consuming unbounded resources and starving other services on a shared node, and enables Texera to run on machines with as little as ~8GB RAM.

Any related issues, documentation, discussions?

closes #4291

How was this PR tested?

Helm chart deployed and verified all pods start successfully with the new resource constraints.

Was this PR authored or co-authored using generative AI tooling?

No

@github-actions github-actions bot added the build label Jan 20, 2026
@chenlica chenlica requested a review from aicam January 20, 2026 04:04
@chenlica
Copy link
Contributor

@SarahAsad23 Please test this PR on your Mac and leave review comments, if any.

@Ma77Ball Ma77Ball changed the title Ball development reduce texera k8 memory usage Chore: Reduce Texera k8 Resources for Development Jan 26, 2026
@Ma77Ball Ma77Ball changed the title Chore: Reduce Texera k8 Resources for Development chore: Reduce Texera k8 Resources for Development Jan 26, 2026
@Ma77Ball
Copy link
Contributor Author

Ma77Ball commented Feb 4, 2026

@bobbai00 and @aicam, please review this pr and let me know if any changes are needed.

@Ma77Ball Ma77Ball force-pushed the Ball-Development-ReduceTexeraK8MemoryUsage branch from 1593dc9 to c55ad0f Compare February 4, 2026 10:51
@Ma77Ball
Copy link
Contributor Author

@bobbai00 or @aicam, please review this pr and let me know if any changes are needed.

Copy link
Contributor

@aicam aicam left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry for the delay

@Ma77Ball
Copy link
Contributor Author

Ma77Ball commented Mar 13, 2026

The workflow runs now. There was an error calling GitHub Actions (not sure why, but it is unrelated to this pr). I will merge soon after merging main into this branch.

@Ma77Ball
Copy link
Contributor Author

@aicam I fixed all the issues please merge

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add resource limits to values.yaml for running Texera on limited hardware

3 participants