starlingx/docs
Code Issues Proposed changes
d466920c10
docs/doc/source/security/kubernetes/configure-remote-cli-access.rst
Joao Victor Portal 191b184763 Review K8s local and remote auth instructions (cherry pick to stx 9.0) 
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>
2024-03-11 10:51:09 -03:00

1.6 KiB
Raw Blame History

Configure Remote CLI Access

You can access the system from a remote workstation using one of two methods.

  • The first method involves using the remote tarball from StarlingX Public build servers to install a set of container-backed remote CLIs and clients for accessing a remote . This provides access to the system and dcmanager CLIs, the OpenStack CLI for Keystone and Barbican in the platform, and Kubernetes-related CLIs (kubectl, helm). This approach is simple to install, portable across Linux, macOS, and Windows, and provides access to all CLIs. However, commands such as those that reference local files or require a shell are difficult to run in this environment.
  • The second method involves installing the kubectl and helm clients directly on the remote host. This method only provides the Kubernetes-related CLIs and requires OS-specific installation instructions.

The helm client has additional installation requirements applicable to either of the above two methods.

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>

Install Kubectl and Helm Clients Directly on a Host <security-install-kubectl-and-helm-clients-directly-on-a-host>