mirror of https://github.com/go-gitea/gitea synced 2024-11-30 13:48:08 +01:00

* chore: add health check endpoint

docs: update document about health check

fix: fix up Sqlite3 ping. current ping will success even if the db file is missing

fix: do not expose privacy information in output field

* refactor: remove HealthChecker struct

* Added `/api/healthz` to install routes.

This was needed for using /api/healthz endpoint in Docker healthchecks,
otherwise, Docker would never become healthy if using healthz endpoint
and users would not be able to complete the installation of Gitea.

* Update modules/cache/cache.go

* fine tune

* Remove unnecessary test code. Now there are 2 routes for installation (and maybe more in future)

Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
Co-authored-by: 6543 <6543@obermui.de>
Co-authored-by: Marcos de Oliveira <marcossantos@furb.br>

2022-05-04 14:56:20 +03:00

1.6 KiB

Raw Blame History

date

title

slug

weight

toc

draft

2020-03-19T19:27:00+02:00

在 Kubernetes 安裝

install-on-kubernetes

false

sidebar

parent	name	weight	identifier
installation	Kubernetes	50	install-on-kubernetes

使用 Helm 安裝 (在 Kubernetes)

Gitea 提供 Helm Chart 用來安裝於 kubernetes。

非自訂安裝可使用下列指令：

helm repo add gitea-charts https://dl.gitea.io/charts/
helm install gitea gitea-charts/gitea

若您想自訂安裝（包括使用 kubernetes ingress），請前往完整的 Gitea helm chart configuration details

##運行狀況檢查終端節點

Gitea 附帶了一個運行狀況檢查端點 /api/healthz，你可以像這樣在 kubernetes 中配置它:

  livenessProbe:
    httpGet:
      path: /api/healthz
      port: http
    initialDelaySeconds: 200
    timeoutSeconds: 5
    periodSeconds: 10
    successThreshold: 1
    failureThreshold: 10

成功的運行狀況檢查回應將使用 HTTP 代碼 200 進行回應，下面是示例:

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"
      }
    ]
  }
}

有關更多信息，請參考kubernetes文檔[定義一個存活態 HTTP請求接口]（https://kubernetes.io/zh/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/）

1.6 KiB Raw Blame History Unescape Escape

使用 Helm 安裝 (在 Kubernetes)

1.6 KiB

Raw Blame History