-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
HA for fully-automatic egress IPs #20485
HA for fully-automatic egress IPs #20485
Conversation
cb88e72
to
369f28a
Compare
/retest |
1 similar comment
/retest |
/retest |
and don't allocate egress IPs to offline nodes
369f28a
to
31c3218
Compare
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
Just some nits.
select { | ||
case <-stop: | ||
return | ||
default: |
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.
Would it be more idomatic to do something like:
var timeout time.Duration
select {
case <-stop:
return
case <-time.After(timeout):
start := time.Now()
retry := eim.check(retry)
if !retry {
// If less than pollInterval has passed since start, then sleep until it has
timeout = time.Until(start.Add(pollInterval))
}
}
/retest |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: danwinship, dcbw The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Tracks node online/offline state and handles reassigning egress IPs as needed.
The tracking code is very similar to the semi-automatic tracking code, but couldn't easily be shared since we don't do the OVS flow tracking in this case. Like the semi-automatic code, it needs to be made more configurable at some point...
@openshift/sig-networking PTAL