airbytehq / airbytehq/airbyte

High availability is not supported for Temporal server

未關閉
#71,186 6 則留言 5 個 reaction 已指派 0 人 在 GitHub 檢視
area/platform autoteam community needs-triage team/compose team/platform-move type/bug
主要語言
Python
星號
22.1k
分支
5.4k
平均合併
5 小時
30 天內合併 PR
671

描述

### Helm Chart Version

2.0.16

### What step the error happened?

On deploy

### Relevant information

The Airbyte Helm chart includes an [option](https://github.com/airbytehq/airbyte-platform/blob/f5f77fd46f2de910201ac55c497edcfd59d96c57/charts/v2/airbyte/templates/airbyte-temporal/deployment.yaml#L15) to run multiple replicas of the Temporal server, however this is impractical due to the lack of support for Temporal's [clustering capabilities](https://docs.temporal.io/references/configuration).

This deployment should be brought closer to parity with Temporal's Helm chart by:
* Including configuration options for server membership in the [server configmap](https://github.com/airbytehq/airbyte-platform/blob/f5f77fd46f2de910201ac55c497edcfd59d96c57/charts/v2/airbyte/templates/airbyte-temporal/configmap.yaml)
* Exposing additional ports for member discovery in the [server deployment](https://github.com/airbytehq/airbyte-platform/blob/f5f77fd46f2de910201ac55c497edcfd59d96c57/charts/v2/airbyte/templates/airbyte-temporal/deployment.yaml#L86-L87)

The official [Temporal Helm chart](https://github.com/temporalio/helm-charts/tree/main) may be used as a reference.

Alternatively, the `temporal.replicaCount` value should be removed and replaced with a fixed value of 1. Documentation should also be updated to indicate that this chart does not support a "production-ready" deployment by most measures out of the box, and offer alternative solutions.

### Relevant log output

```shell
N/A
```

---
**Internal Tracking:** https://github.com/airbytehq/oncall/issues/10809

貢獻指南

開啟貢獻指南

評估

這個 Issue 還沒有評估資料。

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。