temporalio / temporalio/temporal
Adding documentation for self-hosting temporal on cloud environments.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Hi Temporal team!
In my day to day job, we recently tried deploying self-hosted temporal in both AWS EKS and Azure AKS. I found that there's a bunch of gotchas while deploying them. Some of them include:
- Lack of archival support for Azure with storage containers.
- AKS + Azure flexible postgres server fails with lots of tiny errors:
- Azure forces you to have TLS by default, so you have to disable TLS when you deploy it.
- To use visibility store as postgres in Azure, you need to enable BTREE_GIN extension which doesn't come by default.
I thought these might be helpful to add in documentation. Let me know if you think this is worthwhile and please feel free to leave comments.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are identified. Start by locating the existing self-hosting documentation and reviewing the AWS EKS and Azure AKS deployment guidance, including Azure archival storage and PostgreSQL visibility-store requirements; done means the relevant gotchas are documented accurately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, azure, kubernetes, postgresql
- Domain
- cloud, databases, devops, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100