starlingx/docs
Code Issues Proposed changes
docs/doc/source/security/kubernetes/configure-remote-cli-access.rst
Keane Lim 3c5fa979a4 Security guide update 
Re-organized topic hierarchy

Tiny edit to restart review workflow.

Squashed with Resolved index.rst conflict commit

Change-Id: I13472792cb19d1e9975ac76c6954d38054d606c5
Signed-off-by: Keane Lim <keane.lim@windriver.com>
Signed-off-by: MCamp859 <maryx.camp@intel.com>
2021-03-12 15:10:40 -05: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 the CENGEN 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 awkward 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>

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

Configure Remote Helm Client for Non-Admin Users <configure-remote-helm-client-for-non-admin-users>