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
		
			
				
	
	
		
			46 lines
		
	
	
		
			1.7 KiB
		
	
	
	
		
			ReStructuredText
		
	
	
	
	
	
			
		
		
	
	
			46 lines
		
	
	
		
			1.7 KiB
		
	
	
	
		
			ReStructuredText
		
	
	
	
	
	
 | 
						|
.. amd1581954964169
 | 
						|
.. _configure-remote-cli-access:
 | 
						|
 | 
						|
===========================
 | 
						|
Configure Remote CLI Access
 | 
						|
===========================
 | 
						|
 | 
						|
You can access the system from a remote workstation using one of two methods.
 | 
						|
 | 
						|
 | 
						|
.. _configure-remote-cli-access-ul-jt2-lcy-ljb:
 | 
						|
 | 
						|
 | 
						|
-   The first method involves using the remote |CLI| tarball from the
 | 
						|
    |prod| CENGEN build servers to install a set of container-backed remote
 | 
						|
    CLIs and clients for accessing a remote |prod-long|. This provides
 | 
						|
    access to the :command:`system` and :command:`dcmanager` |prod| 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 |prod-long| 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 :command:`kubectl` and
 | 
						|
    :command:`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.
 | 
						|
 | 
						|
.. seealso::
 | 
						|
 | 
						|
    :ref:`Configure Container-backed Remote CLIs and Clients
 | 
						|
    <security-configure-container-backed-remote-clis-and-clients>`
 | 
						|
 | 
						|
    :ref:`Using Container-backed Remote CLIs and Clients
 | 
						|
    <using-container-backed-remote-clis-and-clients>`
 | 
						|
 | 
						|
    :ref:`Install Kubectl and Helm Clients Directly on a Host
 | 
						|
    <security-install-kubectl-and-helm-clients-directly-on-a-host>`
 | 
						|
 | 
						|
    :ref:`Configure Remote Helm v2 Client
 | 
						|
    <configure-remote-helm-client-for-non-admin-users>` |