docs: note that OutlierDetection implicitly activates locality LB failover#3693
docs: note that OutlierDetection implicitly activates locality LB failover#3693yasaswyk wants to merge 1 commit intoistio:masterfrom
Conversation
…lover Affirm-Skill: acli-jira Affirm-Skill: att-deploy-check Affirm-Skill: att-test Affirm-Skill: buildkite-debug Affirm-Skill: capture-context Affirm-Skill: cmt-writer Affirm-Skill: commit-and-push Affirm-Skill: create-adr Affirm-Skill: create-cmt-ticket Affirm-Skill: create-tech-spec Affirm-Skill: export-conversation-record Affirm-Skill: gather-best-practices Affirm-Skill: mcp-debug Affirm-Skill: multi-thor-provisioner Affirm-Skill: resolve-pr-comments Affirm-Skill: save-output Affirm-Skill: security-scanner-for-skill-md Affirm-Skill: skill-evaluator Affirm-Skill: thor-control Affirm-Skill: tickets-from-plan Affirm-Skill: write-implementation-plan
istio-testing
added
the
do-not-merge/work-in-progress
|
😊 Welcome @yasaswyk! This is either your first contribution to the Istio api repo, or it's been You can learn more about the Istio working groups, Code of Conduct, and contribution guidelines Thanks for contributing! Courtesy of your friendly welcome wagon. |
|
|
istio-testing
added
the
size/XS
|
Hi @yasaswyk. Thanks for your PR. I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
istio-testing
removed
the
do-not-merge/work-in-progress
|
/easycla |
3 participants
Adds a note to the
OutlierDetectionmessage doc comment indestination_rule.protoexplaining that because Istio's default mesh config enablesLocalityLbSetting(Enabled:true), configuringOutlierDetectionin aDestinationRuleautomatically activates locality-aware failover — even without an explicitlocalityLbSettingin the rule. Documents the opt-out: setlocalityLbSetting.enabled: falsein the DR's load balancer settings.