docs/doc/source/usertasks/kubernetes/kubernetes-user-tutorials-helm-package-manager.rst
Adil bb5cf99f7b 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
2021-05-12 11:36:53 -03:00

1.1 KiB

Helm Package Manager

supports Helm v3 package manager for Kubernetes that can be used to securely manage the lifecycle of applications within the Kubernetes cluster.

Helm packages are defined by Helm charts with container information sufficient for managing a Kubernetes application. You can configure, install, and upgrade your Kubernetes applications using Helm charts. Helm charts are defined with a default set of values that describe the behavior of the service installed within the Kubernetes cluster.

recommends a non-admin end-user to install a Helm v3 client on a remote workstation to enable management of their Kubernetes applications.

For more information on Helm, see the documentation at https://helm.sh/docs/.

For more information on how to configure and use Helm both locally and remotely, see Configure Local CLI Access <configure-local-cli-access>, and Configure Remote CLI Access <configure-remote-cli-access>.