Browse Source

Patch somes values to be more helm linter compliant

tags/v1.0.1
LecygneNoir 1 year ago
parent
commit
ded55372c6
4 changed files with 7 additions and 7 deletions
  1. +2
    -2
      Chart.yaml
  2. +2
    -2
      templates/deployment.yaml
  3. +1
    -1
      templates/peertube-init.yml
  4. +2
    -2
      values.yaml

+ 2
- 2
Chart.yaml View File

@ -1,5 +1,5 @@
apiVersion: v1
appVersion: "1.0.x"
appVersion: "1.0.1"
description: A Helm chart for Kubernetes
name: peertube
version: 0.1.0
version: 1.0.0

+ 2
- 2
templates/deployment.yaml View File

@ -20,7 +20,7 @@ spec:
release: {{ .Release.Name }}
spec:
initContainers:
- name: initPeertube
- name: init-peertube
image: "{{ .Values.image.repository }}:{{ .Values.image.tag }}"
imagePullPolicy: {{ .Values.image.pullPolicy }}
volumeMounts:
@ -51,7 +51,7 @@ spec:
httpGet:
path: /
port: http
initialDelaySeconds: 90
initialDelaySeconds: 60
command:
- gosu
- peertube

+ 1
- 1
templates/peertube-init.yml View File

@ -3,4 +3,4 @@ kind: ConfigMap
metadata:
name: peertube-init
data:
{{ (.Files.Glob "scripts/peertube-init.sh").AsConfig | indent 2 }}
{{- (.Files.Glob "scripts/peertube-init.sh").AsConfig | nindent 2 }}

sample/values.yml → values.yaml View File

@ -53,7 +53,7 @@ tolerations: []
# values:
# - yournodes.domain.tld
# Currently pvc are not handled by helm, you need to create both config and data volume before launching the helm
# PVC are not handled by helm, you need to create both config and data volume before launching the helm
persistence:
data:
enabled: true
@ -87,7 +87,7 @@ redis:
persistence:
enabled: true
path: /data
# Currently pvc are not handled by helm, you need to create redis volume before deploying helm
# PVC are not handled by helm, you need to create redis volume before deploying helm
persistence:
enabled: true
existingClaim: pvc-redis-prod

Loading…
Cancel
Save