feat: added publicWebUrl to platform helm chart

steadybit · Nov 21, 2023 · 76ffbc3 · 76ffbc3
1 parent 602b7d9
commit 76ffbc3
Show file tree

Hide file tree

Showing 3 changed files with 9 additions and 3 deletions.
diff --git a/charts/steadybit-platform/Chart.yaml b/charts/steadybit-platform/Chart.yaml
@@ -1,13 +1,13 @@
 apiVersion: v2
 name: steadybit-platform
 description: steadybit Platform Helm chart for Kubernetes.
-version: 0.6.8
+version: 0.6.9
 appVersion: latest
 home: https://www.steadybit.com/
 icon: https://steadybit-website-assets.s3.amazonaws.com/logo-symbol-transparent.png
 maintainers:
-  - email: dennis.schulte@steadybit.com
-    name: denschu
+  - email: daniel.reuter@steadybit.com
+    name: Daniel Reuter
 sources:
   - https://github.com/steadybit/helm-charts
 annotations:

diff --git a/charts/steadybit-platform/templates/deployment.yaml b/charts/steadybit-platform/templates/deployment.yaml
@@ -171,6 +171,10 @@ spec:
             - name: STEADYBIT_TENANT_NAME
               value: {{ .Values.platform.tenant.name | quote }}
             {{- end }}
+            {{- if .Values.platform.publicWebUrl }}
+            - name: STEADYBIT_WEB_PUBLIC_URL
+              value: {{ .Values.platform.publicWebUrl }}
+            {{- end }}
             - name: STEADYBIT_WEB_PUBLIC_EXPERIMENT_PORT
               value: {{ .Values.platform.publicWebsocketPort | quote }}
             {{- if .Values.platform.ingressOrigin }}

diff --git a/charts/steadybit-platform/values.yaml b/charts/steadybit-platform/values.yaml
@@ -18,6 +18,8 @@ platform:
           issuerUri: null
   # platform.uiPort -- (internal) Web-UI port for the user interface.
   uiPort: 80
+  # platform.publicWebUrl -- The url where users can access the platform via browser. For example in our SaaS: https://platform.steadybit.com
+  publicWebUrl: null
   # platform.websocketPort -- (internal) Websocket port for communication between platform and agents.
   websocketPort: 7878
   # platform.publicWebsocketPort -- The public port used for experiments - Use this if the agent access the websocket via ingress or a reverse proxy, that serves websocket and http traffic using the same port