Skip to content
This repository has been archived by the owner on Feb 16, 2019. It is now read-only.

Egress rule stops working after Istio was running for 2-3 days. #360

Open
danilina-wsib opened this issue May 28, 2018 · 3 comments
Open
Labels
area/networking kind/bug kind/need more info Need more info or followup from the issue reporter
Milestone

Comments

@danilina-wsib
Copy link

Bug:
Y

What Version of Istio and Kubernetes are you using, where did you get Istio from, Installation details

0.7.1
1.9,6

Is Istio Auth enabled or not ?
No

What happened:
Istio egress rule stops working after Istio was running for a couple of days. Pods suddenly cannot connect to external services. Once Istio pods are restarted, egress rule starts working again. There were new nodes added to the cluster during this time, we are not sure if this has something to do with this.

What you expected to happen:
Egress rule should work

How to reproduce it:
Create an egress rule, leave Istio handle traffic for some time, new pods cannot connect to external servcies

Feature Request:
N

@Archie999
Copy link

I also encountered it. After the current limit was used, it began to operate normally. After a few days, it failed.

@Archie999
Copy link

My tip is upstream connection error or disconnect/reset before title

@sakshigoel12
Copy link
Contributor

@danilina-wsib please upgrade to 0.8 and let us know if you still see this issue

@geeknoid geeknoid removed the kind/bug label Jun 13, 2018
@louiscryan louiscryan added kind/bug kind/need more info Need more info or followup from the issue reporter labels Jun 13, 2018
@louiscryan louiscryan added this to the 1.0 milestone Jun 13, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/networking kind/bug kind/need more info Need more info or followup from the issue reporter
Projects
None yet
Development

No branches or pull requests

5 participants