-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: reword the example in the aggregate cluster docs #37872
Conversation
Docs for this Pull Request will be rendered here: https://storage.googleapis.com/envoy-pr/37872/docs/index.html The docs are (re-)rendered each time the CI |
d72e6aa
to
c05d0ca
Compare
Signed-off-by: Rohit Agrawal <rohit.agrawal@databricks.com>
c05d0ca
to
e4a7250
Compare
priority. | ||
The aggregate cluster load balancer first calculates each priority's health score for every cluster, sums those up, | ||
and then assigns traffic based on the overall total. If the total is at least ``100``, the combined traffic is capped at | ||
``100%``. If it's below ``100``, Envoy scales (normalizes) it so that the final distribution sums to ``100%``. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
our rules are pretty shakey on this, but i think the percentages dont want to be literals - just config settings, response codes, etc - these are actual literals rather than just numbers
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Make sense. So should we leave them as it or should I make them bold using **
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not sure would need to look at it rendered - generally i think boldening (which i like) is mostly useful for skim reading - so if it assists that
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, thanks @agrawroh
Description
This PR rewords the example we have in the aggregate cluster to explain how the cluster level load balancer selects the cluster.
Rendered Docs Link
Commit Message: docs: reword the example in the aggregate cluster docs
Additional Description: Reword the example in aggregate cluster to make it more clear.
Risk Level: N/A
Testing: N/A
Docs Changes: N/A
Release Notes: N/A