Josh Horwitz
Josh Horwitz
The settings manager currently shows this error when you do not have Internet and navigate to the package and/or theme manager.  Once...
Currently the various clients are all structs, which means they are not easily testable. This is going to require consumers of the SDK to implement their own interfaces on top...
It'd be nice if we exposed a way to call the local metadata service since we use this across most of the go projects I'm aware of that use the...
This ensures that the vp will wait for the apiserver to be ready. Currently, if the api server is not ready/available the call to fetch the version will fail and...
Currently we make use of the service's UID. The problem with that is we can't use products like heptio ark to do cluster restores since clients cannot set the UID...
I get the following errors when I run kuberang with an up to date kubectl on v1.11 ``` kubectl version Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.1", GitCommit:"b1b29978270dc22fecc592ac55d903350454310a", GitTreeState:"clean", BuildDate:"2018-07-18T11:36:43Z", GoVersion:"go1.10.3", Compiler:"gc",...
While running kuberang we've noticed scenarios where all the nginx pods will get placed on the same host because of a recent drain/uncordon. In order to get around this it...
It'd be nice to be able to specify kubeconfig values when running kuberang to make dealing with multiple clusters easier. I'm always running kuberang locally on the wrong cluster 👼
For example, simply return "5554441234" instead of "(555) 444-1234" If this sounds good I can code it up / make tests and submit a PR.