Skip to content

[CHORE] Remove chroma-load from k8s to save resources#6410

Open
rescrv wants to merge 2 commits intomainfrom
rescrv/no-load
Open

[CHORE] Remove chroma-load from k8s to save resources#6410
rescrv wants to merge 2 commits intomainfrom
rescrv/no-load

Conversation

@rescrv
Copy link
Contributor

@rescrv rescrv commented Feb 11, 2026

Description of changes

Remove the k8s for chroma-load.

Test plan

CI

Migration plan

N/A

Observability plan

N/A

Documentation Changes

N/A

@github-actions
Copy link

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

  • Can you think of any use case in which the code does not behave as intended? Have they been tested?
  • Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
  • If appropriate, are there adequate property based tests?
  • If appropriate, are there adequate unit tests?
  • Should any logging, debugging, tracing information be added or removed?
  • Are error messages user-friendly?
  • Have all documentation changes needed been made?
  • Have all non-obvious changes been commented?

System Compatibility

  • Are there any potential impacts on other parts of the system or backward compatibility?
  • Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

  • Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

@propel-code-bot
Copy link
Contributor

propel-code-bot bot commented Feb 11, 2026

Remove load-service Kubernetes resources and Tilt build

Eliminates the load-service workload from local Kubernetes tooling to reduce resource consumption. All associated manifests and Tilt build/watch references have been deleted so the service is no longer deployed or built in local/test environments.

Key Changes

• Deleted the entire k8s/test/load-service.yaml manifest, removing the namespace, deployment, config map, and service for load-service
• Removed the custom_build / docker_build blocks for the load-service image in Tiltfile
• Dropped load-service from the k8s_yaml watch list, k8s_resource declarations, and groups['basic'] enablement set in Tiltfile

Possible Issues

• Other tooling or docs might still assume load-service exists, leading to runtime or documentation discrepancies.

This summary was automatically generated by @propel-code-bot

@rescrv rescrv requested a review from jasonvigil February 11, 2026 23:07
@blacksmith-sh

This comment has been minimized.

@blacksmith-sh

This comment has been minimized.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants