You've already forked helm-gitea
Support custom Ingress path (#151)
Adds support for a custom Ingress path. This allows us to run Gitea as a path in an existing domain. Co-authored-by: Matt Kaar <mkaar@cert.org> Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/151 Reviewed-by: luhahn <luhahn@noreply.gitea.io> Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.io> Co-authored-by: mattkaar <mattkaar@noreply.gitea.io> Co-committed-by: mattkaar <mattkaar@noreply.gitea.io>
This commit is contained in:
@ -455,7 +455,9 @@ Annotations can be added to the Gitea pod.
|
||||
|---------------------|-----------------------------------|------------------------------|
|
||||
|ingress.enabled| enable ingress | false|
|
||||
|ingress.annotations| add ingress annotations | |
|
||||
|ingress.hosts| add hosts for ingress as string list | git.example.com |
|
||||
|ingress.hosts[0].host | add hosts for ingress | git.example.com |
|
||||
|ingress.hosts[0].paths[0].path | add path for each ingress host | / |
|
||||
|ingress.hosts[0].paths[0].pathType | add ingress path type | Prefix |
|
||||
|ingress.tls|add ingress tls settings|[]|
|
||||
|
||||
### Service
|
||||
|
Reference in New Issue
Block a user