mirror of
https://github.com/go-gitea/gitea.git
synced 2024-12-04 14:46:57 -05:00
bb25f85ce8
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>
74 lines
1.7 KiB
Markdown
74 lines
1.7 KiB
Markdown
---
|
|
date: "2020-03-19T19:27:00+02:00"
|
|
title: "Install on Kubernetes"
|
|
slug: "install-on-kubernetes"
|
|
weight: 80
|
|
toc: false
|
|
draft: false
|
|
aliases:
|
|
- /en-us/install-on-kubernetes
|
|
menu:
|
|
sidebar:
|
|
parent: "installation"
|
|
name: "Kubernetes"
|
|
weight: 80
|
|
identifier: "install-on-kubernetes"
|
|
---
|
|
|
|
# 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.io/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](https://gitea.com/gitea/helm-chart/)
|
|
|
|
## Health check endpoint
|
|
|
|
Gitea comes with a health check endpoint `/api/healthz`, you can configure it in kubernetes like this:
|
|
|
|
```yaml
|
|
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](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#define-a-liveness-http-request)
|