apiserver-network-proxy icon indicating copy to clipboard operation
apiserver-network-proxy copied to clipboard

Results 120 apiserver-network-proxy issues
Sort by recently updated
recently updated
newest added
trafficstars

Part of our goals here is to allow SSH Tunnels to be removed from the KAS. If we support SSH Tunnels it would allow a smoother migration plan for users...

lifecycle/frozen

when client doesn't send `CloseRequest` to proxy server, due to reasons like reset tunnel or timeout, the proxy server should still recognize it and close the corresponding remote connection.

help wanted
lifecycle/frozen

Currently the proxy-server attempts for forward all connection requests from the client to the proxy-agent. It would be useful to allow the proxy server to have a setting where it...

help wanted
lifecycle/frozen

Currently the proxy server will send all connection requests to a single agent. While all requests for an established connection should go through the same agent on which it was...

lifecycle/frozen

It would be cool to have tracing on the initial dial request, but I think this would require a protocol-level enhancement to `DialResponse` (grpc). The initial flow (happy path) looks...

lifecycle/frozen

We've added a lot of instrumentation around dials, but we have very little instrumentation once the connection is established. Some ideas for metrics to add: - [x] Total data packet...

lifecycle/frozen

If the frontend proxy connection is closed after the connection is established (DIAL_RSP received), but before the frontend sends any data packets, then the backend connection would be leaked: In...

lifecycle/frozen

- This PR refactors how the backends are added to backend manager, but it is working same as before - Instead of multiple backendManagers, use one backendManger - The one...

cncf-cla: yes
ok-to-test
size/XL
needs-rebase

Include the agent ID when fetching a backend, and log the agent ID in relevant locations.

size/M
cncf-cla: yes
needs-rebase