Infrastructure/forgejo
0
Fork 0
mirror of https://codeberg.org/forgejo/forgejo.git synced 2024-12-30 11:23:56 -05:00
Code Issues Activity
forgejo/docs/content/installation/on-kubernetes.zh-tw.md
John Olheiser bd4c7ce578
Docusaurus-ify (#26051) 
This PR cleans up the docs in a way to make them simpler to ingest by
our [docs repo](https://gitea.com/gitea/gitea-docusaurus).

1. It includes all of the sed invocations our ingestion did, removing
the need to do it at build time.
2. It replaces the shortcode variable replacement method with
`@variable@` style, simply for easier sed invocations when required.
3. It removes unused files and moves the docs up a level as cleanup.

---------

Signed-off-by: jolheiser <john.olheiser@gmail.com>
2023-07-26 04:53:13 +00:00

1.7 KiB
Raw Blame History

date title slug sidebar_position toc draft aliases menu
2020-03-19T19:27:00+02:00 在 Kubernetes 安裝 install-on-kubernetes 80 false false
/zh-tw/install-on-kubernetes
sidebar
parent name sidebar_position identifier
installation Kubernetes 80 install-on-kubernetes

使用 Helm 安裝 (在 Kubernetes)

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

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

helm repo add gitea-charts https://dl.gitea.com/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/）