Cornelius Weig
Cornelius Weig
:wave: Hello, maintainer of the kubectl plugin manager [krew](https://github.com/kubernetes-sigs/krew) here. What do you think about making your plugin available via krew? You would benefit from - Greater visibility due krew's...
Kubectl allows to watch for changes to a specific resource, e.g. `kubectl get pod --watch`. Ketall should provide a similar mode to watch _all_ server resources.
Krew tests need a plugin with a small tarball, like `konfig`. However, the krew install currently uses the manually created tarballs for installation, which is bad because the krew tests...
This should support the various options and understand the positional context. Where applicable, it should also suggest context names from the kubeconfig files. Goal: at the very least support bash...
Currently, "split" is an alias for "export". However, the connotation of split is more that the two outcomes have disjoint contexts instead of one being a subset of the other....
Krew tries hard to not break an existing plugin installation, if something during install goes awry. To that end, krew uses symlinks to create a pointer from `$KREW_HOME/bin/kubectl-` into the...
There are basically two patterns in krew: 1. Shadow the outer `t *testing.T`. 2. Use an inner `tt *testing.T` Both variants have their pro's and con's: Shadowing can be confusing...
Currently, we do a plain `git fetch`: https://github.com/kubernetes-sigs/krew/blob/b303e3ae0179431750deab95be05e7b163286c74/pkg/gitutil/git.go#L52-L54 This has some drawbacks, because it * fetches all remote branches and tags * .. and it fetches every commit in each...