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

StatefulSet Pods sometimes lose network connectivity (Calico) -- upgrade to Calico 2.1.5? #2538

Closed
tudor opened this issue May 9, 2017 · 4 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@tudor
Copy link

tudor commented May 9, 2017

We're running a Kubernetes 1.6.2 cluster created with kops 1.6.0-beta.1, and pods occasionally lose network connectivity.

Calico route tables and logs seem to show that we're hitting this Calico bug: https://github.com/projectcalico/calicoctl/issues/1592, which is fixed in calico/cni:v1.7.0, which is part of Calico 2.1.4.

(kops still uses Calico 2.1.1: https://github.com/kubernetes/kops/pull/2286/commits)

Calico 2.1.5 has since been released, so perhaps upgrade to 2.1.5 instead of 2.1.4?

@tudor tudor changed the title Pods sometimes lose network connectivity (Calico) -- upgrade to Calico 2.1.5? StatefulSet Pods sometimes lose network connectivity (Calico) -- upgrade to Calico 2.1.5? May 10, 2017
@ottoyiu
Copy link
Contributor

ottoyiu commented May 13, 2017

I believe Calico 2.1.5 was merged in with:
#2536

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 24, 2017
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle rotten
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 23, 2018
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

4 participants