diff --git a/cluster/addons/e2e-rbac-bindings/e2e-user-binding.yaml b/cluster/addons/e2e-rbac-bindings/e2e-user-binding.yaml
index a71922e53a6..e70d320a902 100644
--- a/cluster/addons/e2e-rbac-bindings/e2e-user-binding.yaml
+++ b/cluster/addons/e2e-rbac-bindings/e2e-user-binding.yaml
@@ -1,6 +1,6 @@
 # This is the main user for the e2e tests.  This is ok to leave long term
 # since the first user in the test can reasonably be high power
-# its kubecfg in gce and kubekins in gke
+# its kubecfg in gce
 # TODO consider provisioning each test its namespace and giving it an
 # admin user.  This still has to exist, but e2e wouldn't normally use it
 apiVersion: rbac.authorization.k8s.io/v1alpha1
@@ -17,6 +17,3 @@ subjects:
 - apiVersion: rbac/v1alpha1
   kind: User
   name: kubecfg
-- apiVersion: rbac/v1alpha1
-  kind: User
-  name: kubekins@kubernetes-jenkins.iam.gserviceaccount.com