mirror of
https://gitea.com/gitea/helm-chart.git
synced 2024-06-01 18:01:24 +05:30
update ha docs
This commit is contained in:
parent
70f6c78bd7
commit
253d4cf2c4
|
@ -93,7 +93,10 @@ When upgrading, please refer to the [Upgrading](#upgrading) section at the botto
|
|||
|
||||
## High Availability
|
||||
|
||||
Deploying a HA-ready Gitea instance requires quite some effort including additional dependencies.
|
||||
Since version 9.0.0 this chart has experimental support for running Gitea and it's dependencies in a HA setup.
|
||||
The setup is still experimental and care must be taken for production use as Gitea core is not yet officially HA-ready.
|
||||
|
||||
Deploying a HA-ready Gitea instance requires some effort including using HA-ready dependencies.
|
||||
See the [HA Setup](docs/ha-setup.md) document for more details.
|
||||
|
||||
## Configuration
|
||||
|
|
|
@ -1,5 +1,7 @@
|
|||
# High Availability
|
||||
|
||||
**Experimental**
|
||||
|
||||
All components (in-memory DB, volume/asset storage, code indexer) used by Gitea must be deployed in a HA-ready fashion to achieve a full HA-ready Gitea deployment.
|
||||
The following document explains how to achieve this for all individual components.
|
||||
|
||||
|
@ -167,5 +169,7 @@ gitea:
|
|||
|
||||
## Known issues
|
||||
|
||||
Currently Cron jobs are run on all replicas as no leader election is implemented.
|
||||
See [https://github.com/go-gitea/gitea/issues/13791](https://github.com/go-gitea/gitea/issues/13791) for a discussion and possible solution.
|
||||
- Currently Cron jobs are run on all replicas as no leader election is implemented.
|
||||
See [https://github.com/go-gitea/gitea/issues/13791](https://github.com/go-gitea/gitea/issues/13791) for a discussion and possible solution.
|
||||
|
||||
- Running with multiple replicas slows down Gitea a bit, i.e. page loading time increases.
|
Loading…
Reference in a new issue