From 169ac6c8c88bc1bcb20726a6fc508424b157f40d Mon Sep 17 00:00:00 2001
From: Guy Shilo <52055301+guyShilo@users.noreply.github.com>
Date: Tue, 5 Sep 2023 18:48:39 +0300
Subject: [PATCH] [chore] Update CluserRole & CluserRoleBinding apiVersions
 (#24834)

**Description:** <Describe what has changed.>
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->

**Link to tracking Issue:** <Issue number if applicable>

**Testing:** <Describe what testing was performed and which tests were
added.>

**Documentation:** <Describe the documentation added.>
---
 receiver/k8seventsreceiver/README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/receiver/k8seventsreceiver/README.md b/receiver/k8seventsreceiver/README.md
index 70c74e2c2d45..862784469b22 100644
--- a/receiver/k8seventsreceiver/README.md
+++ b/receiver/k8seventsreceiver/README.md
@@ -105,7 +105,7 @@ Use the below commands to create a `ClusterRole` with required permissions and a
 
 ```bash
 <<EOF | kubectl apply -f -
-apiVersion: rbac.authorization.k8s.io/v1beta1
+apiVersion: rbac.authorization.k8s.io/v1
 kind: ClusterRole
 metadata:
   name: otelcontribcol
@@ -173,7 +173,7 @@ EOF
 
 ```bash
 <<EOF | kubectl apply -f -
-apiVersion: rbac.authorization.k8s.io/v1beta1
+apiVersion: rbac.authorization.k8s.io/v1
 kind: ClusterRoleBinding
 metadata:
   name: otelcontribcol