apiserver-network-proxy
apiserver-network-proxy copied to clipboard
kubernetes-sigs
Currently each konnectivity agent can only connect to a single konnectivity server which makes the konnectivity server a single failure point. One option is using VIP to fail over between...
Currently, I believe this information is only available in the cli flag `--server-count`. It would be nice to have this information propagated as prometheus metric as well.
Currently, releasing a new version tag is cumbersome (https://github.com/kubernetes-sigs/apiserver-network-proxy/blob/master/RELEASE.md). Manual steps: - create version tags - create image promotion PRs - bump k/k client library and example manifests * and...
ProxyServer [addBackend](https://github.com/kubernetes-sigs/apiserver-network-proxy/blob/master/pkg/server/server.go#L258-L295) (and removeBackend) don't check errors, and could have stronger separation of concerns.
I'm not sure if my understanding is correct or not but the the number of proxy servers created should reflect serverCount value. https://github.com/kubernetes-sigs/apiserver-network-proxy/blob/fd446dc21dcca7b0674315a60ade29d642175c33/tests/proxy_test.go#L868 Similarly not sure why serverCount would be...
TODO
Currently the agent and server are not honouring the change of TLS certificates provided to them. This PR introduces a file watcher for both agent and server to restart the...
Create version tags for: https://github.com/kubernetes-sigs/apiserver-network-proxy/pulls?q=is%3Apr+is%3Aclosed+v0.17.0 ```[tasklist] ### Tasks - [x] Create tag 0.28.1 - [x] Create tag 0.28.2 - [x] Create tag 0.1.6 - [x] Create tag 0.1.7 - [x]...
Script the current release process. (Draft only - maybe there's a better approach altogether)
If proxy-server explicitly mentions `default` as one of the proxy-strategy along with others, then all agents are added to the DefaultBackendManager despite an agent having `agent-identifers` set corresponding to default-route...