element-call-helm

An experimental helm chart deploying a full element-call instance
git clone git://archive.git.mtrnord.blog/MTRNord/element-call-helm.git
Log | Files | Refs | README

commit 5dd1eeae4e18905e7be3ef360f79bc48de0ace78
parent 090f4b0cead4a14d3d4060dab38775df2132bac4
Author: MTRNord <mtrnord1@gmail.com>
Date:   Wed,  6 Mar 2024 10:46:00 +0100

Fix some urls in the config

Diffstat:
Mcharts/element-call/Chart.yaml | 2+-
Mcharts/element-call/templates/deployment_livekit_mgmt_service.yaml | 2+-
Mcharts/element-call/values.yaml | 23+++++++++++++++--------
3 files changed, 17 insertions(+), 10 deletions(-)

diff --git a/charts/element-call/Chart.yaml b/charts/element-call/Chart.yaml @@ -2,7 +2,7 @@ apiVersion: v2 name: element-call description: A Helm chart for element_call type: application -version: 0.1.0 +version: 0.1.1 appVersion: "v0.5.15" dependencies: diff --git a/charts/element-call/templates/deployment_livekit_mgmt_service.yaml b/charts/element-call/templates/deployment_livekit_mgmt_service.yaml @@ -37,7 +37,7 @@ spec: imagePullPolicy: {{ .Values.livekit_mgmt.image.pullPolicy }} env: - name: LIVEKIT_URL - value: ws://{{ include "livekit-server.fullname" . }}:{{ index .Values "livekit-server" "livekit" "port" }} + value: ws://{{ include "element_call.fullname" . }}-livekit-server:{{ index .Values "livekit-server" "livekit" "port" }} - name: LIVEKIT_KEY value: {{ .Values.livekit_key }} - name: LIVEKIT_SECRET diff --git a/charts/element-call/values.yaml b/charts/element-call/values.yaml @@ -29,10 +29,12 @@ element_call: podAnnotations: {} podLabels: {} - podSecurityContext: {} + podSecurityContext: + {} # fsGroup: 2000 - securityContext: {} + securityContext: + {} # capabilities: # drop: # - ALL @@ -46,7 +48,8 @@ element_call: ingress: enabled: false className: "" - annotations: {} + annotations: + {} # kubernetes.io/ingress.class: nginx # kubernetes.io/tls-acme: "true" hosts: @@ -59,7 +62,8 @@ element_call: # hosts: # - chart-example.local - resources: {} + resources: + {} # We usually recommend not to specify default resources and to leave this as a conscious # choice for the user. This also increases chances charts run on environments with little # resources, such as Minikube. If you do want to specify resources, uncomment the following @@ -110,10 +114,12 @@ livekit_mgmt: podAnnotations: {} podLabels: {} - podSecurityContext: {} + podSecurityContext: + {} # fsGroup: 2000 - securityContext: {} + securityContext: + {} # capabilities: # drop: # - ALL @@ -124,7 +130,8 @@ livekit_mgmt: service: type: ClusterIP - resources: {} + resources: + {} # We usually recommend not to specify default resources and to leave this as a conscious # choice for the user. This also increases chances charts run on environments with little # resources, such as Minikube. If you do want to specify resources, uncomment the following @@ -199,7 +206,7 @@ egress: # CHANGE ME api_key: devkey api_secret: secret - ws_url: ws://{{ include "livekit-server.fullname" . }}:{{ index .Values "livekit-server" "livekit" "port" }} + ws_url: changeme insecure: true redis: