2021-01-29 01:57:58 +01:00
|
|
|
|
---
|
|
|
|
|
|
date: "2020-03-19T19:27:00+02:00"
|
|
|
|
|
|
title: "在 Kubernetes 安裝"
|
|
|
|
|
|
slug: "install-on-kubernetes"
|
2023-07-26 06:53:13 +02:00
|
|
|
|
sidebar_position: 80
|
2021-01-29 01:57:58 +01:00
|
|
|
|
toc: false
|
|
|
|
|
|
draft: false
|
Refactor docs (#23752)
This was intended to be a small followup for
https://github.com/go-gitea/gitea/pull/23712, but...here we are.
1. Our docs currently use `slug` as the entire URL, which makes
refactoring tricky (see https://github.com/go-gitea/gitea/pull/23712).
Instead, this PR attempts to make future refactoring easier by using
slugs as an extension of the section. (Hugo terminology)
- What the above boils down to is this PR attempts to use directory
organization as URL management. e.g. `usage/comparison.en-us.md` ->
`en-us/usage/comparison/`, `usage/packages/overview.en-us.md` ->
`en-us/usage/packages/overview/`
- Technically we could even remove `slug`, as Hugo defaults to using
filename, however at least with this PR it means `slug` only needs to be
the name for the **current file** rather than an entire URL
2. This PR adds appropriate aliases (redirects) for pages, so anything
on the internet that links to our docs should hopefully not break.
3. A minor nit I've had for a while, renaming `seek-help` to `support`.
It's a minor thing, but `seek-help` has a strange connotation to it.
4. The commits are split such that you can review the first which is the
"actual" change, and the second is added redirects so that the first
doesn't break links elsewhere.
---------
Signed-off-by: jolheiser <john.olheiser@gmail.com>
2023-04-28 05:33:41 +02:00
|
|
|
|
aliases:
|
|
|
|
|
|
- /zh-tw/install-on-kubernetes
|
2021-01-29 01:57:58 +01:00
|
|
|
|
menu:
|
|
|
|
|
|
sidebar:
|
|
|
|
|
|
parent: "installation"
|
|
|
|
|
|
name: "Kubernetes"
|
2023-07-26 06:53:13 +02:00
|
|
|
|
sidebar_position: 80
|
2021-01-29 01:57:58 +01:00
|
|
|
|
identifier: "install-on-kubernetes"
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
|
|
# 使用 Helm 安裝 (在 Kubernetes)
|
|
|
|
|
|
|
|
|
|
|
|
Gitea 提供 Helm Chart 用來安裝於 kubernetes。
|
|
|
|
|
|
|
|
|
|
|
|
非自訂安裝可使用下列指令：
|
|
|
|
|
|
|
|
|
|
|
|
```
|
2023-06-21 05:11:17 +02:00
|
|
|
|
helm repo add gitea-charts https://dl.gitea.com/charts/
|
2021-01-29 01:57:58 +01:00
|
|
|
|
helm install gitea gitea-charts/gitea
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
若您想自訂安裝（包括使用 kubernetes ingress），請前往完整的 [Gitea helm chart configuration details](https://gitea.com/gitea/helm-chart/)
|
2022-05-04 13:56:20 +02:00
|
|
|
|
|
2022-07-28 03:22:47 +02:00
|
|
|
|
## 運行狀況檢查終端節點
|
2022-05-04 13:56:20 +02:00
|
|
|
|
|
|
|
|
|
|
Gitea 附帶了一個運行狀況檢查端點 `/api/healthz`，你可以像這樣在 kubernetes 中配置它:
|
|
|
|
|
|
|
|
|
|
|
|
```yaml
|
|
|
|
|
|
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/）
|
