Eddie Zaneski

icon indicating an email [email protected]

icon company @DefenseUnicorns icon location Denver, CO icon location sig-cli @kubernetes | oss @defenseunicorns

Results 158 comments of Eddie Zaneski

`kubectl version` takes 35s if context is unreachable

Also it's worth calling out that there is a `kubectl version --client=true` flag to skip the server check.

kubectl delete leaks network connections when deleting multiple resources, causing warnings or errors

This may be fixed on the upcoming 1.23 release or by https://github.com/kubernetes/kubernetes/pull/105723. You might be able to temporarily fix this by [raising the ulimit on your mac](https://wilsonmar.github.io/maximum-limits/). @ash2k this might...

kubectl delete leaks network connections when deleting multiple resources, causing warnings or errors

/assign atiratree

kubectl delete leaks network connections when deleting multiple resources, causing warnings or errors

Great reproduction example in https://github.com/kubernetes/kubectl/issues/1152

kubectl exec & port forward TLS handshake error when https_proxy environment variable contains special characters

@mwalexander82 are you able to reproduce this on version 1.17 or higher?

kubectl exec & port forward TLS handshake error when https_proxy environment variable contains special characters

/reopen @mjoshi89 please tell more about the proxy you're using. Which one? Version? Anything else of note?

kubectl exec & port forward TLS handshake error when https_proxy environment variable contains special characters

@mjoshi89 the more you can provide to help us reproduce the better.

Improve documentation of kubectl top

/priority backlog

Consider provide kubectl-plugin-scaffolding repository as a public template for Go

Hi @Dentrax! We discussed this today during our bi-weekly meeting and don't think we need to add another repo but would love for y'all to upstream some of these suggestions...

Consider provide kubectl-plugin-scaffolding repository as a public template for Go

Apologies for the delay here. If you're still interested in working on this please feel free to open smaller PRs against the existing repo. Especially when it comes CI/vendor implementations...