add priority to workload entry #3619
Conversation
Signed-off-by: Rama Chavali <rama.rao@salesforce.com>
|
😊 Welcome @ramaraochavali! 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
zirain
added
the
release-notes-none
howardjohn
left a comment
howardjohn
left a comment
There was a problem hiding this comment.
How does this relate to the many many other 'priority' mechanisms we have? what if its priority=3 but in another region with locality LB enabled?
This seems like it could be done today with DR failoverPriority? https://istio.io/latest/docs/reference/config/networking/destination-rule/#LocalityLoadBalancerSetting-failover_priority
I do not think this can be solved by DR. This is for endpoints matched by a DNS cluster. So they do not have k8s labels associated.
The priority specified here would be taken in to consideration for DNS endpoints specified overriding the locality LB specified in DR. As I mentioned, this is mainly useful for workloadentries specified via DNS resolution to implement failover across two DNS clusters. |
What do you mean? Its a WorkloadEntry, it has labels? |
5 participants
Adds priority to workload entry. This is especially useful to setup active/passive between two clusters defined by two different DNS based clusters. When endpoints in priority(0), becomes unhealthy - traffic automatically moves to priority1.