You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: containers/kubernetes/how-to/revoke-kubeconfig.mdx
+1-1
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ By the end of 2023, a new Authentication (Auth) system, based on IAM tokens, is
24
24
25
25
Previously, users were limited to static admin tokens provisioned by Kapsule.
26
26
27
-
In the new system, when an employee loses access rights (e.g., leaves the organization), the Kubernetes administrator can simply modify the IAM group, edit its policy, or remove the user to revoke cluster access.
27
+
In the new system, when a user loses access rights (e.g., leaves the organization), the Kubernetes administrator can simply modify the IAM group, edit its policy, or remove the user to revoke cluster access.
28
28
This approach is a derivation from the previous method, where the owner had to reset the admin token, impacting all other users and requiring actions through the Console, CLI, or API methods.
29
29
Now, users have the alternative option of using a key provisioned by IAM for authentication.
0 commit comments