Skip to content

Issues: kubernetes-sigs/apiserver-network-proxy

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.

Sign up for GitHub

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

42 Open 158 Closed
42 Open 158 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Incorrect link for Kubernetes api server kind/bug Categorizes issue or PR as related to a bug. kind/documentation Categorizes issue or PR as related to documentation.
#680 opened Dec 9, 2024 by kundan2707
@kundan2707
2
agents should get lease namespace and label details from server in connect metadata instead of passing as cli flags
#673 opened Nov 7, 2024 by ipochi
panic: lease controller system if not using token auth.
#671 opened Oct 26, 2024 by ipochi
3
Create 0.31.x release (branch and tags)
#657 opened Oct 2, 2024 by jkh52
6 of 7 tasks
@cheftako
1
Use information from lease WATCH system to respond to added/removed servers more quickly lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
#648 opened Aug 20, 2024 by carreter
2
Konnectivity server is incompatible with go std lib
#645 opened Aug 7, 2024 by steeling
3
Ensure webhook availability during Konnectivity Agent rolling update lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#566 opened Feb 16, 2024 by dippynark
@jkh52
10
FR: support routing strategy "failure zone" lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#543 opened Nov 30, 2023 by jkh52
6 tasks
2
FR: streamline release overhead lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#542 opened Nov 28, 2023 by jkh52
3
Prometheus metric to say how many konectivity-server are there lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#521 opened Sep 6, 2023 by ipochi
@ipochi
6
Version skew testing triage/accepted Indicates an issue or PR is ready to be actively worked on.
#519 opened Aug 30, 2023 by tallclair
1 of 6 tasks
@tallclair
3
Clarity on konnectivity - kubernetes supported version matrix lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#474 opened Mar 8, 2023 by ipochi
@jkh52
3
Protocol: simplify identifers lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#462 opened Feb 14, 2023 by jkh52
10
add "konnectivity" to readme or repo tags for SEO lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#461 opened Feb 14, 2023 by BenTheElder
@jkh52
2
Further improve agent log levels (avoid spurious errors) lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#449 opened Jan 11, 2023 by jkh52
5
[FR] Consider dial protocol tracing lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#411 opened Oct 5, 2022 by tallclair
2
Improve post-dial instrumentation lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#410 opened Oct 5, 2022 by tallclair
2 of 5 tasks
2
DIAL_CLS / DIAL_RSP race leading to connection leak lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#404 opened Sep 16, 2022 by tallclair
5
Support for multiple server addresses on agent lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#394 opened Aug 30, 2022 by jnummelin
@cheftako
10
Add benchmarks & stress tests needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. triage/accepted Indicates an issue or PR is ready to be actively worked on.
#366 opened Jun 23, 2022 by tallclair
7 tasks
@tallclair
8
Improve dynamic server count detect logic of agent lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#358 opened May 31, 2022 by zqzten
11
Need a way to seamlessly rotate the Proxy Server Certs on the Agent side. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#350 opened Apr 11, 2022 by cheftako
6
[BUG] The backend ServerMetric is not correct lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#294 opened Nov 24, 2021 by YRXING
2
@jkh52
9
Support dynamic number of proxy-servers lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#273 opened Oct 15, 2021 by jkh52
@cheftako @caesarxuchao
19
Konnectivity server leaks memory and free sockets lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#255 opened Aug 10, 2021 by Tamas-Biro1
1
26
ProTip! Add no:assignee to see everything that’s not assigned.