Commit f9a59dc1 authored by James Gregory's avatar James Gregory Committed by Sean Knox

[stable/kapacitor] Fixes broken Persistent Volume support (#670)

* Fix pvc metadata The `chart` and `name` keys are in the wrong place. * Fix indentation for persistent volume * [stable/kapacitor] bump chart version to 0.2.2 * fix test flake
parent 1167bf42
name: kapacitor name: kapacitor
version: 0.2.1 version: 0.2.2
description: InfluxDB's native data processing engine. It can process both stream and batch data from InfluxDB. description: InfluxDB's native data processing engine. It can process both stream and batch data from InfluxDB.
keywords: keywords:
- kapacitor - kapacitor
......
...@@ -34,10 +34,10 @@ spec: ...@@ -34,10 +34,10 @@ spec:
{{ toYaml .Values.resources | indent 12 }} {{ toYaml .Values.resources | indent 12 }}
volumes: volumes:
- name: data - name: data
{{ if .Values.persistence.enabled }} {{- if .Values.persistence.enabled }}
persistentVolumeClaim: persistentVolumeClaim:
claimName: {{ template "fullname" . }} claimName: {{ template "fullname" . }}
{{ else }} {{- else }}
emptyDir: {} emptyDir: {}
{{ end }} {{- end }}
{{- end }} {{- end }}
...@@ -2,12 +2,12 @@ ...@@ -2,12 +2,12 @@
kind: PersistentVolumeClaim kind: PersistentVolumeClaim
apiVersion: v1 apiVersion: v1
metadata: metadata:
chart: "{{ .Chart.Name }}-{{ .Chart.Version }}" name: {{ template "fullname" . }}
labels: labels:
chart: "{{ .Chart.Name }}-{{ .Chart.Version }}"
release: "{{ .Release.Name }}" release: "{{ .Release.Name }}"
heritage: "{{ .Release.Service }}" heritage: "{{ .Release.Service }}"
app: {{ template "fullname" . }} app: {{ template "fullname" . }}
name: {{ template "fullname" . }}
annotations: annotations:
{{- if .Values.persistence.storageClass }} {{- if .Values.persistence.storageClass }}
volume.beta.kubernetes.io/storage-class: {{ .Values.persistence.storageClass | quote }} volume.beta.kubernetes.io/storage-class: {{ .Values.persistence.storageClass | quote }}
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment