Use v1 instead of v1beta1 for ClusterRoleBinding 🤖

Starting in 1.17, using `ClusterRoleBinding` with rbac.authorization.k8s.io/v1beta1 is deprecated and will be removed in 1.22. Let's use `v1` API instead. Signed-off-by: Vincent Demeester <[email protected]>
tekton-robot · Mar 29, 2021 · fd30912 · fd30912
1 parent 46372f3
commit fd30912
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/config/201-clusterrolebinding.yaml b/config/201-clusterrolebinding.yaml
@@ -12,7 +12,7 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 
-apiVersion: rbac.authorization.k8s.io/v1beta1
+apiVersion: rbac.authorization.k8s.io/v1
 kind: ClusterRoleBinding
 metadata:
   name: tekton-pipelines-controller-cluster-access
@@ -33,7 +33,7 @@ roleRef:
 # then the ClusterRole would be namespaced. The access described by
 # the tekton-pipelines-controller-tenant-access ClusterRole would
 # be scoped to individual tenant namespaces.
-apiVersion: rbac.authorization.k8s.io/v1beta1
+apiVersion: rbac.authorization.k8s.io/v1
 kind: ClusterRoleBinding
 metadata:
   name: tekton-pipelines-controller-tenant-access
@@ -50,7 +50,7 @@ roleRef:
   name: tekton-pipelines-controller-tenant-access
   apiGroup: rbac.authorization.k8s.io
 ---
-apiVersion: rbac.authorization.k8s.io/v1beta1
+apiVersion: rbac.authorization.k8s.io/v1
 kind: ClusterRoleBinding
 metadata:
   name: tekton-pipelines-webhook-cluster-access