Skip to content

Commit 5d2157f

Browse files
bene2k1RoRoJ
andauthored
Apply suggestions from code review
Co-authored-by: Rowena Jones <[email protected]>
1 parent a784c83 commit 5d2157f

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ If your Organization uses IAM to control access, ensure that you or your group/a
3434

3535
To create a new policy with the correct permission sets, follow these steps:
3636

37-
### Key elements of IAM Policy configuration
37+
### Configure an IAM policy
3838

3939
1. **Create a new policy**: Navigate to the **Policies** tab in your Organization’s IAM console and create a new policy.
4040
2. **Add your user (or group/application)**: Assign your user, group, or application as the **Principal**.
@@ -61,7 +61,7 @@ If you have not set up the Scaleway CLI yet:
6161
```bash
6262
scw init
6363
```
64-
You will need your [API Key](/identity-and-access-management/iam/how-to/create-api-keys/) (access key & secret key).
64+
You will need your [API Key](/identity-and-access-management/iam/how-to/create-api-keys/) (access key and secret key).
6565

6666

6767
### Retrieve and install the kubeconfig using scw
@@ -104,7 +104,7 @@ To revoke a user's access to the cluster, ensure that any API keys associated wi
104104
#### Reassign the user to a restricted group
105105
- Transfer the principal (application or user) to a group with reduced permissions that does not allow cluster access.
106106

107-
#### Delete the Principal
107+
#### Delete the principal
108108
- Permanently remove the user or application from the IAM system to ensure no further access is possible.
109109

110110
### Revoking kubeconfig access

0 commit comments

Comments
 (0)