191b184763
This change replaces the usage of Service Tokens by OIDC tokens in the instructions of Kubernetes cluster local and remote access. Some other changes were made, like the deletion of redundant pages. Story: 2010738 Task: 49561 Change-Id: Ie8206ecd316efd356a5889899a68f9a9ddbcdfa6 Signed-off-by: Joao Victor Portal <Joao.VictorPortal@windriver.com>
1.7 KiB
Install Kubectl and Helm Clients Directly on a Host
You can use kubectl and helm to interact with a controller from a remote
system.
Commands such as those that reference local files or commands that require a shell are more easily used from clients running directly on a remote workstation.
Complete the following steps to install kubectl and helm on a remote
system.
The following procedure shows how to configure the kubectl and helm
clients directly on remote host, for an admin user with
cluster-admin cluster role. If using a non-admin user
such as one with only role privileges within a private namespace, the
procedure is the same, however, additional configuration is required in
order to use helm.
You must configure the oidc-auth-apps Identity
Provider (dex) on the target environment to get Kubernetes
authentication tokens. See Set up OIDC Auth Applications <configure-oidc-auth-applications>
for more information.
Configure Container-backed Remote CLIs and Clients
<security-configure-container-backed-remote-clis-and-clients>
Using Container-backed Remote CLIs and Clients
<using-container-backed-remote-clis-and-clients>