Open astoycos opened 1 year ago
We talked about this in a sync, @astoycos says connection tracking helps are now available in the kernel, so as a part of this effort we should switch from our narrow and focused connection tracking to using the upstream facilities in the kernel.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
As it pertains to https://github.com/aya-rs/aya/discussions/505 our ingress/egress code is becoming quite complex, and uses a fair amount of info() calls. Given https://github.com/aya-rs/aya/discussions/505#discussioncomment-4806350 we should take some time and refactor this to reduce complexity and number of aya-log calls.