No configuration file and no GUI
Before you authenticate:
Review cluster access options from the console.
Install the
kubectl-shturval-plugincluster access module. See the module installation instructions.After you install the
kubectl-shturval-pluginmodule, runkubectl shturval login, substituting your parameter values, to download kubeconfigs for the clusters available to the user.
Available options for the kubectl shturval login command
| Parameter | Required | Description |
|---|---|---|
--auth-url [string] | no | Authentication server URL |
--cacert [string] | no | Contents of the root trusted certificate |
--cacert-file [string] | no | Path to the root trusted certificate |
--client-id [string] | no | Client ID for the authentication service. Default: backend |
--client-secret [string] | yes | Secret client for authentication service |
-n, --cluster-name [string] | no | Name of the cluster to get kubeconfig. Not specified if you need to get kubeconfigs of all clusters |
--config-path [string] | no | Path to the location of the shturval-login-plugin.yaml configuration file. Default for Linux: /root |
-i, --insecure | no | TLS connection security check sign |
-k, --kubeconfig [string] | no | Path to downloaded kubeconfigs. Default for Linux: /root/.kube/config |
-p, --password [string] | no | Password for connecting to the shturval-backend server. If your password contains special characters ($,<, >, *, &, ?, /,\ ), you must escape them using single quotes. For example, --password='my$Password?'. |
-s, --server-url [string] | yes, if there is no configuration file or the URL is not specified in it | shturval-backend server URL |
--ttl [string] | no | Token lifetime. Default 24h |
-u, --username [string] | yes, if there is no configuration file or the username is not specified in it | Username for connecting to the shturval-backend server |
-v, --version | no | login command version |
- Once the clusters’ kubeconfigs are loaded, you can manage the available clusters using the kubectl utility commands.
Please note! After calling the command without a connection password (parameter -p / --password), it will be requested interactively.
Screenshot of an example password request
Examples of loading cluster kubeconfigs for the user without a configuration file
1. Command to load cluster kubeconfigs with specified account parameters without password, shturval-backend server URL, client secret for authentication service and without TLS connection security check
kubectl shturval login --username=ENTER-USERNAME-FOR-CONNECTION --server-url=ENTER-shturval-backend-SERVER-URL --insecure=true --client-secret=ENTER-AUTHENTICATION-SERVICE-CLIENT-SECRET
In --client-secret enter the value of the backend secret key backend-
2. Command to load kubeconfigs of clusters with specified account parameters, shturval-backend server URL, client secret for authentication service and TLS connection security check enabled (root certificate specified)
kubectl shturval login --username=ENTER-USERNAME-FOR-CONNECTION --password='ENTER-USER-PASSWORD' --server-url=ENTER-shturval-backend-SERVER-URL --client-secret=ENTER-AUTHENTICATION-SERVICE-CLIENT-SECRET --cacert=-----BEGIN CERTIFICATE-----Base64 content-----END CERTIFICATE-----
In --client-secret enter the value of the backend secret key backend-
3. Command to load cluster kubeconfigs with specified account parameters, shturval-backend server URL, client secret for the authentication service and TLS connection security check enabled (the path to the root trusted certificate is specified)
kubectl shturval login --username=ENTER-USERNAME-FOR-CONNECTION --password='ENTER-USER-PASSWORD' --server-url=ENTER-shturval-backend-SERVER-URL --client-secret=ENTER-AUTHENTICATION-SERVICE-CLIENT-SECRET --cacert-file=ENTER-PATH-TO-ROOT-TRUSTED-CERTIFICATE
In --client-secret enter the value of the backend secret key backend-
4. The command to load kubeconfigs of clusters without checking the security of the TLS connection, with the specified directory for loading kubeconfigs of the available clusters
kubectl shturval login --username=ENTER-USERNAME-FOR-CONNECTION --password='ENTER-USER-PASSWORD' --server-url=ENTER-shturval-backend-SERVER-URL --insecure=true --client-secret=ENTER-AUTHENTICATION-SERVICE-CLIENT-SECRET --kubeconfig=ENTER-PATH-FOR-kubeconfig-DOWNLOAD
In --client-secret enter the value of the backend secret key backend-
5. Command to load kubeconfig of one cluster with specified mandatory authentication parameters, a password for connecting to the shturval-backend server, without checking the security of the TLS connection
kubectl shturval login --username=ENTER-USERNAME-FOR-CONNECTION --password='ENTER-USER-PASSWORD' --server-url=ENTER-shturval-backend-SERVER-URL --client-secret=ENTER-AUTHENTICATION-SERVICE-CLIENT-SECRET --cluster-name=myclustername --insecure=true
In --client-secret enter the value of the backend secret key backend-
6. Command to load kubeconfig of one cluster with specified required authentication parameters, TLS connection security check
kubectl shturval login --username=ENTER-USERNAME-FOR-CONNECTION --password='ENTER-USER-PASSWORD' --server-url=ENTER-shturval-backend-SERVER-URL --client-secret=ENTER-AUTHENTICATION-SERVICE-CLIENT-SECRET --cluster-name=ENTER-CLUSTER-NAME --cacert-file=ENTER-PATH-TO-ROOT-TRUSTED-CERTIFICATE
In --client-secret enter the value of the backend secret key backend-
If you encounter access errors, you can find a way to solve the problem in the next section Actions in case of common access errors.