-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Pull virtual IPs for filter chains from discovery chains #17375
Conversation
27e38ec
to
a9a5d97
Compare
agent/xds/listeners.go
Outdated
@@ -232,6 +232,15 @@ func (s *ResourceGenerator) listenersFromSnapshotConnectProxy(cfgSnap *proxycfg. | |||
// We do not match on all endpoints here since it would lead to load balancing across | |||
// all instances when any instance address is dialed. | |||
for _, e := range endpoints { | |||
if chain.Partition == e.Service.PartitionOrDefault() { |
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.
Ignore my last approval. In failover scenarios (where there may be zero endpoints), this would remove the chain's VIP from the config, right? So we should probably hoist the attachment of the chain outside of this loop.
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.
Do we still need this logic here if the code above is always attaching the VIPs?
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 how that got left in, it's gone now
a9a5d97
to
f479922
Compare
f479922
to
99d5b0c
Compare
This PR is a follow-up to previous work that adds logic in
xds
to pull virtual IPs from discovery chains - including both auto-assigned and manually set (such as cluster IPs via kubernetes).