-
Notifications
You must be signed in to change notification settings - Fork 11
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
Pepr Watch is not Responding to Changes after 90 mins #745
Comments
here is a temporary workaround that should force the watcher pod to reconnect. https://gist.github.com/cmwylie19/2c07e0e6f0962b8f18999488d1646a4a |
something with the AWS VPC CNI could have issues and is sometimes dropping policy. It could have something to do with it. Related Issue - aws/amazon-vpc-cni-k8s#2103 |
Fixed by #766. If you experience this, use the environment variable |
Some seemingly related issues:
Possible solution/workaround in istio/istio#8696 (comment) by creating a |
This is not technically resolved and setting a very low resync threshold like this is a really bad practice in production. Agree we either need to look at dropping Istio for this or looking at |
This should be solved based on c0d3aaa and the KFC informer pattern. All soak tests have passed |
Environment
Device and OS: UDS Core
App version:
Watch controller started responding after rolling. Only pod logs were health checks
Kubernetes distro being used:
Other: EKS Kubernetes 1.29
Steps to reproduce
Expected result
Upon disconnection, it reconnects
Actual Result
Visual Proof (screenshots, videos, text, etc)
Severity/Priority
Additional Context
Add any other context or screenshots about the technical debt here.
Well Known Bug:
kubernetes-client/csharp#533
kubernetes-client/javascript#596
The text was updated successfully, but these errors were encountered: