{"id":36262,"date":"2023-06-28T09:00:59","date_gmt":"2023-06-28T09:00:59","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=36262"},"modified":"2023-06-28T09:01:02","modified_gmt":"2023-06-28T09:01:02","slug":"helm-tutorials-global-values-in-helm-chart","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/helm-tutorials-global-values-in-helm-chart\/","title":{"rendered":"Helm Tutorials: Global Values in Helm Chart"},"content":{"rendered":"\n

In Helm, you can define global values that are accessible across all templates within a chart. Global values are useful for defining configuration settings or variables that are common to multiple templates or can be shared across different parts of your chart.<\/p>\n\n\n\n

To define global values in a Helm chart, follow these steps:<\/p>\n\n\n\n

Step 1: Create or Modify the values.yaml<\/code> File<\/h2>\n\n\n\n

In your chart’s root directory, open or create the values.yaml<\/code> file. This file is where you can define your chart’s default values and override them during installation or upgrade.<\/p>\n\n\n\n

Step 2: Define Global Values<\/h2>\n\n\n\n

Inside the values.yaml<\/code> file, add a section for your global values. For example:<\/p>\n\n\n

global<\/span>:\r\n  app<\/span>:\r\n    name<\/span>: my-app<\/span>\r\n    version<\/span>: 1.0<\/span>.0<\/span>\r\n  environment<\/span>: production<\/span>\r\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
In this example, we have defined two global values: app<\/code> and environment<\/code>. The app<\/code> value is a nested object with two properties, name<\/code> and version<\/code>, while environment<\/code> is a simple string value.<\/p>\n\n\n\n
Step 3: Accessing Global Values in Templates<\/h2>\n\n\n\n
To access the global values in your chart’s templates, you can use the .Values.global<\/code> object. For example, to access the app.name<\/code> global value in a template, you can use {{ .Values.global.app.name }}<\/code>.<\/p>\n\n\n\n
Here’s an example of how you can use a global value in a template:<\/p>\n\n\n\n
\n\n\n
apiVersion: v1\r\nkind: Service\r\nmetadata:\r\n  name: {{ .Values.global<\/span>.app.name }}-service\r\nspec:\r\n  selector:\r\n    app: {{ .Values.global<\/span>.app.name }}\r\n  ports:\r\n    - name: http\r\n      port: 80<\/span>\r\n      targetPort: 8080<\/span>\r\n  type: LoadBalancer\r\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
In this example, we are using the global value app.name<\/code> to dynamically generate the service name.<\/p>\n\n\n\n
Step 4: Installing or Upgrading the Chart<\/h2>\n\n\n\n
When installing or upgrading the chart, you can override the global values by providing a custom values.yaml<\/code> file or passing individual values using the --set<\/code> flag.<\/p>\n\n\n\n
For example, to override the global environment<\/code> value during installation, you can use the following command:<\/p>\n\n\n\n
helm install my-chart .\/my-chart –set global.environment=staging<\/p>\n\n\n\n
This will set the environment<\/code> value to “staging” instead of the default “production”.<\/p>\n\n\n\n
That’s it! You now know how to define and use global values in a Helm chart.<\/p>\n","protected":false},"excerpt":{"rendered":"
In Helm, you can define global values that are accessible across all templates within a chart. Global values are useful for defining configuration settings or variables that… <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[2],"tags":[],"class_list":["post-36262","post","type-post","status-publish","format-standard","hentry","category-uncategorised"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/36262","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=36262"}],"version-history":[{"count":1,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/36262\/revisions"}],"predecessor-version":[{"id":36263,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/36262\/revisions\/36263"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=36262"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=36262"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=36262"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}