Skip to content

Commit d386a81

Browse files
committed
docs(k8s): update rbac information
1 parent fa08071 commit d386a81

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

pages/kubernetes/how-to/connect-cluster-kubectl.mdx

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,11 +34,12 @@ If your Organization uses IAM to control access, ensure that you or your group/a
3434
- `KubernetesFullAccess` (or `KubernetesReadOnly`, depending on your needs):
3535
Grants you the ability to manage (or list/read) Kubernetes clusters, nodes, and related actions in your Scaleway Project.
3636

37+
If you do not have configured IAM for your account yet, you can generate a `kubeconfig` file with IAM and required permission sets after cluster creation from the Scaleway console.
38+
3739
<Message type="tip">
38-
If you do not have setup IAM for your account yet, you can generate a `kubeconfig` file with IAM after cluster creation from the Scaleway console.
40+
For detailed information about the configuration of IAM policies for your Kubernetes clusters, refer to our dedicated documentation [Setting IAM permissions and implementing RBAC on a cluster](/kubernetes/reference-content/set-iam-permissions-and-and-implement-rbac/).
3941
</Message>
4042

41-
For detailed information about the configuration of IAM policies for your Kubernetes clusters, refer to our dedicated documentation [Setting IAM permissions and implementing RBAC on a cluster](/kubernetes/reference-content/set-iam-permissions-and-and-implement-rbac/).
4243
## Accessing the cluster
4344

4445
You can use the Scaleway CLI to automatically retrieve (and merge) your `kubeconfig` file, then interact with your Kubernetes cluster.

0 commit comments

Comments
 (0)