[bitnami/*] Extra manifests should be top-level (#4161)

extra manifests declared with the `extraDeploy` value used to be defined in a single List manifest.
the issue with this setup, is that if you want to define a Job to be used as a Helm hook, it won't work - because Helm only look at top-level manifests to find the hook annotations.

this PR changes the implementation of extra manifests, by rendering top-level manifests instead of wrapping them inside a List.
charts users don't need to change anything in their values.yaml
This commit is contained in:
Vincent Behar
2020-10-30 14:11:06 +01:00
committed by GitHub
parent 181a02f5a9
commit b3a95b701b
37 changed files with 75 additions and 94 deletions

View File

@@ -1,6 +1,6 @@
apiVersion: v1
name: consul
version: 8.0.3
version: 8.0.4
appVersion: 1.8.4
description: Highly available and distributed service discovery and key-value store designed with support for the modern data center to make distributed systems and configuration easy.
home: https://github.com/bitnami/charts/tree/master/bitnami/consul

View File

@@ -1,5 +1,4 @@
{{- if .Values.extraDeploy }}
apiVersion: v1
kind: List
items: {{- include "common.tplvalues.render" (dict "value" .Values.extraDeploy "context" $) | nindent 2 }}
{{- range .Values.extraDeploy }}
---
{{ include "common.tplvalues.render" (dict "value" . "context" $) }}
{{- end }}