Any recommendations on how to enable Temporal UI for Airbyte v2? added in values.yaml, but still not able to access from the UI

temporalUi:
  enabled: True

The knowledge sources you provided don’t contain explicit instructions for enabling or exposing the Temporal UI in Airbyte v2, beyond showing that

temporal-ui.enabled

is a valid Helm value in some example configurations. [[Worker bean issue](https://github.com/airbytehq/airbyte/issues/60915)] From what is shown: - In the older chart examples,

temporal-ui

is enabled via a top‑level

temporal-ui.enabled: true

block, not

temporalUi.enabled

. [[Worker bean issue](https://github.com/airbytehq/airbyte/issues/60915)] - The v2 values reference docs only link to the full

values.yaml

on GitHub and don’t document a

temporalUi

key or how the UI is exposed (service type, ingress, etc.). [[Values reference](https://docs.airbyte.com/platform/deploying-airbyte/values); [Values reference next](https://docs.airbyte.com/platform/next/deploying-airbyte/values)] Because of that, I can’t confidently confirm that

temporalUi.enabled: true

is the correct key or that enabling it alone will make the UI reachable in v2. Given these limits, here are the only safe recommendations based on the sources: 1. Verify the exact key name and structure in the v2 chart’s

values.yaml

on GitHub (linked from the docs) and mirror that structure rather than using

temporalUi:

. [[Values reference](https://docs.airbyte.com/platform/deploying-airbyte/values); [Values reference next](https://docs.airbyte.com/platform/next/deploying-airbyte/values)] 2. Check that a

temporal-ui

Deployment/Service is actually created after you set the value and upgrade the release. 3. Confirm how it’s exposed (ClusterIP vs NodePort/Ingress). The docs show how to port‑forward the Airbyte server, but they don’t document a similar command for Temporal UI, so you may need to inspect the service and manually

kubectl port-forward

it. [[Port forward guide](https://docs.airbyte.com/platform/deploying-airbyte#6-set-up-port-forward-for-ui-access)] If you can share the exact

values.yaml

section from the chart (from the linked GitHub file) and your rendered resources (

kubectl get deploy,svc -n <ns>

), I can help you interpret them, but I can’t provide a precise key or URL path for Temporal UI from the current knowledge sources.

@kapa.ai Which is the default port for the Temporal UI?

A message from kapa.ai