Skip to content

fix: web ui uses internalFrontend when available#724

Open
golgoth31 wants to merge 1 commit intotemporalio:mainfrom
golgoth31:fix/web-ui-uses-internal-frontend
Open

fix: web ui uses internalFrontend when available#724
golgoth31 wants to merge 1 commit intotemporalio:mainfrom
golgoth31:fix/web-ui-uses-internal-frontend

Conversation

@golgoth31
Copy link
Copy Markdown

What was changed

This pull request allow the web ui to use the internal frontend when it's available.

Why?

With the current configuration the web ui is only linked to the common frontend, when anabling authorization on this frontend, the UI is enable to work properly. Using the internal frontend allows using a different OIDC provider for jwt access then the jwt authorization in the frontend.

Checklist

  1. Closes [Feature Request] Temporal UI use internal-frontend #706

  2. How was this tested:
    deployed and working in our system.

  3. Any docs updates needed?

@golgoth31 golgoth31 requested a review from a team as a code owner July 10, 2025 13:13
@CLAassistant
Copy link
Copy Markdown

CLAassistant commented Jul 10, 2025

CLA assistant check
All committers have signed the CLA.

@CLAassistant
Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Signed-off-by: David Sabatie <david.sabatie@notrenet.com>
@golgoth31 golgoth31 force-pushed the fix/web-ui-uses-internal-frontend branch from ebf6967 to fc44bdb Compare July 10, 2025 15:35
imagePullPolicy: {{ .Values.web.image.pullPolicy }}
env:
- name: TEMPORAL_ADDRESS
{{- if and (hasKey .Values.server "internalFrontend") .Values.server.internalFrontend.enabled .Values.web.useInternalFrontend }}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
{{- if and (hasKey .Values.server "internalFrontend") .Values.server.internalFrontend.enabled .Values.web.useInternalFrontend }}
{{- if and (index .Values.server "internal-frontend").enabled .Values.web.useInternalFrontend }}

env:
- name: TEMPORAL_ADDRESS
{{- if and (hasKey .Values.server "internalFrontend") .Values.server.internalFrontend.enabled .Values.web.useInternalFrontend }}
value: "{{ include "temporal.fullname" $ }}-internal-frontend.{{ .Release.Namespace }}.svc:{{ .Values.server.internalFrontend.service.port }}"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
value: "{{ include "temporal.fullname" $ }}-internal-frontend.{{ .Release.Namespace }}.svc:{{ .Values.server.internalFrontend.service.port }}"
value: {{ include "temporal.fullname" $ }}-internal-frontend:{{ (index $.Values.server "internal-frontend").service.port }}

@robholland robholland added the needs revision Team has requested some changes label Apr 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs revision Team has requested some changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature Request] Temporal UI use internal-frontend

3 participants