Skip to content
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

Handle backend watch, if upstream closes channel[ClosedByRemote] #1247

Merged
merged 1 commit into from
Jul 22, 2020

Conversation

krishgobinath
Copy link
Contributor

@krishgobinath krishgobinath commented Jun 5, 2020

This PR handles following things.

If upstream Kubernetes API server closes watch the channel with backend libcalico-go, then stop the backend channels connected downstream and don't send any "ErrorTerminated" events back to downstream channels.

If upstream Kubernetes API server, sends Api.WatchError to backend libcalico-go, wrap this status change as an "ApiError" to downstream. Downstream will resync the channel.

Local Unit test passed.

@krishgobinath krishgobinath changed the title Update syncer Handle backend watch, if upstream closes channel[ClosedByRemote] Jun 5, 2020
Copy link
Contributor

@robbrockbank robbrockbank left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@ravilr
Copy link

ravilr commented Oct 29, 2020

@krishgobinath @robbrockbank the changes to etcdv3/watcher.go in this PR seems to have broken calico using etcd backend, under certain error scenarios. : projectcalico/calico#4109
Can you please check..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants