starlingx/docs
Code Issues Proposed changes
Files
8c59671f510a93fc3420b87b328bc01204d9f16d
docs/doc/source/security/kubernetes/configure-remote-cli-access.rst
Adil 818110b309 Added content related to Helm v3 
Included information from msg attached to Jira in
Edited content in Admin tasks and User tasks

Patch 1: worked on comments by Greg.

Patch 4: added User task to the correct branch

Patch 5: worked on feedback from Greg also in other topics
Edited content in: -helm client for non-admin users
		   -container backed remote clis and clients
		   -install kebectl and helm clients on a host

Patch 6: edited and added content in
 		   -helm client for non-admin users

Patch 7: Added content in: Configure remote CLI
			   Configure container-backed...
			   Use container-backed...

Patch 10: acted on Jim's comment and
	removed topic 'create, test, and terminate a ptp notification demo'
	removed links to this topic

Patch 11: acted on Greg's comments

Patch 12: acted on Greg's comments

Story: 2007000
Task: 42241

https://review.opendev.org/c/starlingx/docs/+/783891

Signed-off-by: Adil <mohamed.adilassakkali@windriver.com>

Change-Id: I9a5faf5549775593ddfd517d43412725d257b24f
(cherry picked from commit bb5cf99f7b)
Signed-off-by: Adil <mohamed.adilassakkali@windriver.com>
2021-05-14 16:44:07 -03: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 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>

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>