mirror of
https://codeberg.org/forgejo/forgejo.git
synced 2024-11-01 06:48:56 +00:00
b217ce3e9f
See https://github.com/go-gitea/gitea/pull/26051
---------
Signed-off-by: jolheiser <john.olheiser@gmail.com>
Co-authored-by: JonRB <4564448+eeyrjmr@users.noreply.github.com>
(cherry picked from commit 4033d95dbf
)
1.7 KiB
1.7 KiB
date | title | slug | sidebar_position | toc | draft | aliases | menu | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
2020-03-19T19:27:00+02:00 | Install on Kubernetes | install-on-kubernetes | 80 | false | false |
|
|
Installation with Helm (on Kubernetes)
Gitea provides a Helm Chart to allow for installation on kubernetes.
A non-customized install can be done with:
helm repo add gitea-charts https://dl.gitea.com/charts/
helm install gitea gitea-charts/gitea
If you would like to customize your install, which includes kubernetes ingress, please refer to the complete Gitea helm chart configuration details
Health check endpoint
Gitea comes with a health check endpoint /api/healthz
, you can configure it in kubernetes like this:
livenessProbe:
httpGet:
path: /api/healthz
port: http
initialDelaySeconds: 200
timeoutSeconds: 5
periodSeconds: 10
successThreshold: 1
failureThreshold: 10
a successful health check response will respond with http code 200
, here's example:
HTTP/1.1 200 OK
{
"status": "pass",
"description": "Gitea: Git with a cup of tea",
"checks": {
"cache:ping": [
{
"status": "pass",
"time": "2022-02-19T09:16:08Z"
}
],
"database:ping": [
{
"status": "pass",
"time": "2022-02-19T09:16:08Z"
}
]
}
}
for more information, please reference to kubernetes documentation Define a liveness HTTP request