Jesse Glick

Specifically I would expect colorization on `get -o yaml` and `get -o json`. At least for the latter, you can work around this by ```sh kubectl get -o json $type...

This seems like a bad idea. You are replacing a limited token good only for connecting this agent with a general personal access token which, if compromised, could be abused...

I think resolved in https://github.com/jenkinsci/docker-slave/pull/95.

> Can we add a test case as well? Probably above my skill level.

This is just a side effect of some other (properly reported) error: there is code which tries to clean up by stopping a service which in this case had not...

I think this remains valid.

Rebased as suggestion. https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_controller-runtime/1785/pull-controller-runtime-test-master/1485692352398888960 is opaque to me.

I would suggest that #238 be the way forward. Although Google Cloud does not yet advertise it, you can authenticate to GKE from `kubectl` without using any vendor-specific plugin: ```yaml...

https://github.com/jenkins-infra/helpdesk/issues/2629 now?

> supports `aws-iam-authenticator` as of `4.1.0` Beware that 4.1.1 is broken in this regard.