diff --git a/src/renderer/components/+add-cluster/add-cluster.tsx b/src/renderer/components/+add-cluster/add-cluster.tsx index 9245926029..0350cdcd6b 100644 --- a/src/renderer/components/+add-cluster/add-cluster.tsx +++ b/src/renderer/components/+add-cluster/add-cluster.tsx @@ -169,12 +169,11 @@ export class AddCluster extends React.Component {
Add clusters by clicking the Add Cluster button. - You'll need to obtain a working kubeconfig for the cluster you want to add. + You'll need to obtain a working kubeconfig for the cluster you want to add. You can either browse it from the file system or paste it as a text from the clipboard.
- Each cluster context is added as a separate item in the - left-side cluster menu - to allow you to operate easily on multiple clusters and/or contexts. + Selected cluster contexts are added as a separate item in the + left-side cluster menu to allow you to operate easily on multiple clusters and/or contexts.
For more information on kubeconfig see Kubernetes docs. @@ -189,20 +188,6 @@ export class AddCluster extends React.Component { When connecting to a cluster, make sure you have a valid and working kubeconfig for the cluster. Following lists known "gotchas" in some authentication types used in kubeconfig with Lens app.
- -- When connecting Lens to OIDC enabled cluster, there's few things you as a user need to take into account. -
-Dedicated refresh token
-
- As Lens app utilized kubeconfig is "disconnected" from your main kubeconfig Lens needs to have it's own refresh token it utilizes.
- If you share the refresh token with e.g. kubectl who ever uses the token first will invalidate it for the next user.
- One way to achieve this is with kubelogin tool by removing the tokens
- (both id_token and refresh_token) from
- the config and issuing kubelogin command. That'll take you through the login process and will result you having "dedicated" refresh token.
-
When using exec auth plugins make sure the paths that are used to call