Comments (2)
It seems the stream is getting torn every few minutes. Can you tell how often that happens, and whether that interval of time is consistent? Besides the log entries, is this causing changes in policy resources (Server, HTTPRoute, AuthorizationPolicy, etc) to not being detected?
from linkerd2.
The errors are logged every 5 or 10 minutes (either of those, not a range) for about an hour. Sometimes, all the resource's watchers fail around the same time. Sometimes, they take turns: HTTP Routes fail for one hour, then MeshTlsAuthentications fail for another hour.
The last log entry was six hours ago, though.
I don't directly use those resources; we only have the default resources created during installation. Any way to test this out?
from linkerd2.
Related Issues (20)
- Proxy trying to connect to no-longer available endpoints HOT 4
- .
- Enable OpenSSF Scorecard to enhance security practices across the project HOT 2
- "Operation not permitted" error in linkerd-proxy on edge-24.6.4 HOT 12
- Better documentation on the expectations for `networkValidator.connectAddr` for `linkerd-control-plane` helm chart values HOT 4
- Linkerd Destination Pod Unhealthy Warnings HOT 2
- Healthchecks/livenessProbe does not pass when using HTTPS scheme HOT 3
- The "Debugging HTTP applications with per-route metrics" task in the documentation is broken and needs updating
- Not all gRPC errors should be retried HOT 3
- Traffic split not working with ExternalName services / services in different namespaces HOT 1
- Linkerd CNI repair controller does not listen on IPv6 HOT 1
- Setting `-log-level debug` introduces `client-go` logging at the `INFO` level HOT 1
- Improve `linkerd viz check` to have skip prom clusterrole checks when prom controller is disabled
- Increase startup and liveness probe timeout for linkerd-destination HOT 2
- linkerd/client image cannot be found on cr.l5d.io (ghcr.io) HOT 1
- linkerd-proxy does not evict idle metrics eventually leading to OOMKILL HOT 5
- Linkerd-proxy routing traffic to wrong pod HOT 5
- Allow setting LINKERD2_PROXY_SHUTDOWN_ENDPOINT_ENABLED in helm chart HOT 5
- linkerd-proxy: allow to add custom headers to outgoing requests
- Outbound HTTP endpoints seems to miscount "ready" endpoints with circuit breaking HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from linkerd2.