Helm: Retrieve Installed Chart Values **NOTE:** This title is optimized for SEO with the primary keyword "helm" placed at the beginning, followed by the secondary keyword "installed chart values." It is also concise and catchy to attract users searching for this topic.

When working with Kubernetes, retrieving the values of an installed chart is a crucial operation to understand the current configuration of your application. This process, known as "helm get values," allows you to introspect your chart and verify the parameters you've set. Let's delve into this process and explore it in detail.

a flow diagram showing the steps to create an action plan for a company's organization

Before we begin, ensure you have Helm installed and initialized, and your chart is already deployed. If not, you can install Helm using its official documentation guide and deploy a chart using the Helm command "helm install."

Understanding Helm Chart Directory Structure for Kubernetes Package Manager|Helm Tutorial for DevOps

Understanding Helm Get Values Command

The "helm get values" command is used to retrieve the values currently in use by your deployed chart. It's essential to understand the differences between this command and "helm get" or "helm show values." While "helm get values" provides the current values, "helm get" can give you information about resources, and "helm show values" displays the default values as declared in your chart's value file.

the safety helmet code is shown in different colors

Now, let's explore the various parameters and executions of the "helm get values" command.

Basic Usage

construction helmet safety poster with instructions for helmets and their meaning in blue, yellow, red, orange, green, brown or black

The simplest way to fetch values is by specifying the release name:

helm get values <release-name>

Replace "<release-name>" with the name of your deployed release. This command will display the current values used by that specific release.

Example: ```bash helm get values my-release ```

Using Specific Namespace

If your release is deployed to a specific Kubernetes namespace, you can run:

helm get values <release-name> --namespace <namespace-name>

This helps when dealing with multiple clusters or namespaces.

Now, let's discuss some additional commands and their uses.

Additional Commands and Parameters

the construction helmet color code is shown

the safety helmets guide for construction workers is shown in this graphic above it's description

an info sheet with the words creating customer value in different colors and shapes, including circles

different types of hard hats are shown in this graphic diagram, which includes the names and colors

Helm Operations and ShipTracks Launch Competitor Jobs Tracking Capability

helm get values <chart-name> <chart-version>

This retrieves the default or custom values from your local or repository chart.

Fetching Values While Installing

During installation, you can fetch values with:

helm install <release-name> <chart> -f <values-file> --generate-name -o yaml

The "-o yaml" flag outputs the values in YAML format.

In the next section, we'll elaborate on how to handle custom values with "helm get values" command.

Working with Custom Values

When you've overridden default values with custom values using a values file (like -f), "helm get values" will display the combined output of default and custom values used during installation. If you want to see only the custom values, use the "--show-only" flag:

helm get values <release-name> --show-only

To retrieve all values in JSON format, use the "--output json" option:

helm get values <release-name> --output json

This is particularly useful when you need to parse the output in scripting environments or CI/CD pipelines.

The "helm get values" command provides a straightforward way to introspect your chart, fetch current values, and ensure your application is running as intended. Regularly using this command will help keep your deployments consistent and predictable. As you continue your Kubernetes journey, always remember to keep an eye on your application's values to maintain full control over your environment.