Fix inherit examples following #674 (#815)

This commit is contained in:
stoned 2023-04-18 23:56:29 +02:00 committed by GitHub
parent 1ddba549d3
commit 4aeb0ff6f2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 6 additions and 6 deletions

View File

@ -27,11 +27,11 @@ releases:
- name: heapster - name: heapster
version: 0.3.2 version: 0.3.2
inherit: inherit:
template: default - template: default
- name: kubernetes-dashboard - name: kubernetes-dashboard
version: 0.10.0 version: 0.10.0
inherit: inherit:
template: default - template: default
``` ```
2. release values template 2. release values template
@ -40,7 +40,7 @@ releases:
- name: some-release - name: some-release
chart: my-chart chart: my-chart
values: values:
# This is a template file can use the built-in objects # This is a template file can use the built-in objects
- path/to/values.gotmpl - path/to/values.gotmpl
``` ```
@ -62,4 +62,4 @@ releases:
The built-in values always begin with a capital letter. This is in keeping with The built-in values always begin with a capital letter. This is in keeping with
Go's naming convention. When you define your own values and template variables, you are free to use a Go's naming convention. When you define your own values and template variables, you are free to use a
convention that suits your team. convention that suits your team.

View File

@ -103,11 +103,11 @@ releases:
- name: heapster - name: heapster
version: 0.3.2 version: 0.3.2
inherit: inherit:
template: default - template: default
- name: kubernetes-dashboard - name: kubernetes-dashboard
version: 0.10.0 version: 0.10.0
inherit: inherit:
template: default - template: default
``` ```
Release Templating supports the following parts of release definition: Release Templating supports the following parts of release definition: