Add agent scaling, routing, and deployment guidance#585
Draft
pstreef wants to merge 4 commits into
Draft
Conversation
Expand agent configuration docs with sizing rules of thumb, per-agent resource recommendations, deployment environment guidance (VMs vs K8s), and proxy cross-references. Expand the routing reference with detailed routing mechanics, operation routing table, capability splitting guide, and common pitfalls.
- Reword misleading "recipe runs queue" bullet to clarify agents don't run recipes - Remove unsupported "4-6 VMs" claim that conflicts with sizing guidance - Add downtime tradeoff note to Recreate strategy recommendation
When multiple agents configure the same tool (e.g. same GitHub URL), their credentials must be identical because requests shuffle across matching agents. A multi-step OAuth flow can span agents and will fail if credentials differ.
- Replace "shuffle and try" with "round-robin" in routing docs (simpler mental model for customers) - Consistent trailing periods on K8s bullet points
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
1 participant
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.
Problem
Customers frequently ask how many agents to deploy, how traffic is distributed, whether agents can be split by responsibility, and whether to use VMs or Kubernetes. These questions came up with various customers. The existing docs cover basic mechanics but lack operational guidance.
Solution
agent-config.md — expand the scaling section with:
routing-requests-to-agents.md — add three new sections: