From 7f2d33dfdfa1b5da97e78d666c9f67a0c35e4867 Mon Sep 17 00:00:00 2001 From: deads2k Date: Thu, 22 Dec 2016 09:32:00 -0500 Subject: [PATCH] add kubekins as cluster-admin --- .../{kubecfg-binding.yaml => e2e-user-binding.yaml} | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) rename cluster/addons/e2e-rbac-bindings/{kubecfg-binding.yaml => e2e-user-binding.yaml} (76%) diff --git a/cluster/addons/e2e-rbac-bindings/kubecfg-binding.yaml b/cluster/addons/e2e-rbac-bindings/e2e-user-binding.yaml similarity index 76% rename from cluster/addons/e2e-rbac-bindings/kubecfg-binding.yaml rename to cluster/addons/e2e-rbac-bindings/e2e-user-binding.yaml index 8bad467245a..a71922e53a6 100644 --- a/cluster/addons/e2e-rbac-bindings/kubecfg-binding.yaml +++ b/cluster/addons/e2e-rbac-bindings/e2e-user-binding.yaml @@ -1,11 +1,12 @@ # 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 # 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 kind: ClusterRoleBinding metadata: - name: kubecfg-cluster-admin + name: e2e-user-cluster-admin labels: kubernetes.io/cluster-service: "true" roleRef: @@ -16,3 +17,6 @@ subjects: - apiVersion: rbac/v1alpha1 kind: User name: kubecfg +- apiVersion: rbac/v1alpha1 + kind: User + name: kubekins@kubernetes-jenkins.iam.gserviceaccount.com