Carolina Buckler
12/17/2025, 5:45 PMkapa.ai
12/17/2025, 5:46 PMbash helm repo add airbyte-v2 <https://airbytehq.github.io/charts> helm repo update [[Add repo](https://docs.airbyte.com/platform/deploying-airbyte#1-add-the-helm-repository)] 2. Install Airbyte with the matching V2 chart (for 2.0.0 the example is chart `2.0.18`; you’d pick the chart whose APP VERSION is 2.0.1 for your case): bash helm search repo airbyte-v2 --versions # find the row where APP VERSION is 2.0.1, note its CHART VERSION helm install airbyte airbyte-v2/airbyte \ --namespace airbyte-v2 \ --values ./values.yaml \ --version <matching-chart-version> [[Helm install V2](https://docs.airbyte.com/platform/deploying-airbyte#5-installing-airbyte)] However, the knowledge sources do not contain any instructions specific to starting or exposing the Temporal UI when using Helm chart V2 for Airbyte 2.0.x. They only describe how to port‑forward the Airbyte UI (deployment/airbyte-server) on V2 deployments, e.g.: bash kubectl -n airbyte-v2 port-forward deployment/airbyte-server 8080:8001 [[Port‑forward UI](https://docs.airbyte.com/platform/deploying-airbyte#6-set-up-port-forward-for-ui-access)] There is no documented command, service name, or deployment name for the Temporal UI in the V2 chart in the provided materials, and no mention of a separate temporal-ui component for chart V2. So, based on the available documentation, I’m sorry, but there’s no information about how to start or access the Temporal UI specifically for Airbyte 2.0.1 with Helm chart V2.Carolina Buckler
12/17/2025, 5:46 PMkapa.ai
12/17/2025, 5:47 PMkapa.ai
12/17/2025, 5:47 PMdeployment/airbyte-server) [[Port‑forward UI](https://docs.airbyte.com/platform/deploying-airbyte#6-set-up-port-forward-for-ui-access); [Ingress via Helm](https://docs.airbyte.com/platform/deploying-airbyte/integrations/ingress#option-1-use-airbytes-helm-chart)]. - A Terraform snippet that creates a kubernetes_service "temporal" of type ExternalName, but this is just an example from a closed GitHub issue and not Helm‑V2‑specific UI guidance [[GH issue 68134](https://github.com/airbytehq/airbyte/issues/68134)]. There is no explicit mention in these sources of: - A Temporal UI deployment or service name in Helm chart V2. - Any documented port‑forward or ingress configuration for a Temporal UI in Airbyte 2.0.x. So, based on the available knowledge sources, I cannot reliably say how to start or access the Temporal UI for **Airbyte 2.0.1 with Helm chart V2**; the docs simply don’t document it.