Utilize bjw-s's common
Helm library. #13
|
@ -17,11 +17,7 @@ service:
|
|||
{{- end }}
|
||||
port: 80
|
||||
protocol: HTTP
|
||||
|
||||
targetPort: 8080
|
||||
|
||||
env:
|
||||
- name: VIKUNJA_SERVICE_INTERFACE
|
||||
value: ":8080"
|
||||
|
||||
{{ end }}
|
||||
|
||||
|
|
12
values.yaml
12
values.yaml
|
@ -12,7 +12,6 @@ env:
|
|||
VIKUNJA_DATABASE_DATABASE: "{{ .Values.postgresql.global.postgresql.auth.database }}"
|
||||
# -- You should provide your own secret outside of this helm-chart and use `postgresql.global.postgresql.auth.existingSecret` to provide credentials to the postgresql instance
|
||||
VIKUNJA_DATABASE_PASSWORD: "{{ .Values.postgresql.global.postgresql.auth.password }}"
|
||||
VIKUNJA_TYPESENSE_ENABLED: "{{ .Values.typesense.enabled }}"
|
||||
VIKUNJA_TYPESENSE_APIKEY: "{{ .Values.typesense.env.TYPESENSE_API_KEY }}"
|
||||
VIKUNJA_TYPESENSE_URL: '{{ printf "%s-typesense" .Release.Name }}'
|
||||
VIKUNJA_FRONTEND_URL: '{{ printf "http://%s-frontend" .Release.Name }}'
|
||||
|
@ -72,7 +71,7 @@ backend:
|
|||
|
||||
# Dependencies
|
||||
postgresql:
|
||||
enabled: false
|
||||
enabled: true
|
||||
global:
|
||||
postgresql:
|
||||
auth:
|
||||
|
@ -89,18 +88,19 @@ redis:
|
|||
typesense:
|
||||
enabled: true
|
||||
env:
|
||||
TYPESENSE_DATA_DIR: /tsdata
|
||||
TYPESENSE_DATA_DIR: /data
|
||||
TYPESENSE_API_KEY: typesense
|
||||
persistence:
|
||||
tsdata:
|
||||
data:
|
||||
# Enabling typesense persistence is recommended to avoid slow reindexing
|
||||
enabled: false
|
||||
enabled: true
|
||||
accessMode: ReadWriteOnce
|
||||
size: 1Gi
|
||||
# storageClass: storage-class
|
||||
|
||||
image:
|
||||
repository: docker.io/typesense/typesense
|
||||
tag: 0.24.0
|
||||
tag: 0.25.1
|
||||
pullPolicy: IfNotPresent
|
||||
|
||||
serviceAccount:
|
||||
|
|
Loading…
Reference in New Issue
What if the api ingress is using https?
By default,
ingress-nginx
redirects HTTP to HTTPS and the annotationnginx.ingress.kubernetes.io/force-ssl-redirect: "true"
can be used with other Kubernetes Ingress objects to redirect HTTP to HTTPS. It's "normal" in the deployments I've created to have to create that annotation on the Ingress if I've required that redirection (or the other way around :))