starlingx/docs
Code Issues Proposed changes
docs/doc/source/security/kubernetes/configure-remote-cli-access.rst
Ron Stone b7e75df19b Recommended "renewBefore" value for a certificate (r8, r7, r5, r5, dsR8, dsR7, dsR6, dsR5) 
Add note as include
Add include where renewBefore is mentioned
Address patchset 1 review comments

Closes-Bug: 2042545

Change-Id: Iad4f58fd2cd4743605089b453ededce1e720c8e9
Signed-off-by: Ron Stone <ronald.stone@windriver.com>
2023-11-07 15:03:24 +00:00

1.7 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>

Configure Remote Helm v2 Client <configure-remote-helm-client-for-non-admin-users>