You've already forked helm-gitea
The following patch adds support for network policies. The patch does not contain any specific network policies, as it is uncertain in which environment and with which access rights gitea will be deployed. With regard to third-party components such as PostgreSQL or Valkey, the network policy may need to be adjusted. Whether this happens directly in the helm chart or whether the user has to enter it themselves is open to discussion. During testing, I defined a few sample network policies to get Gitea up and running. These are only examples. Reviewed-on: https://gitea.com/gitea/helm-gitea/pulls/952 Reviewed-by: DaanSelen <daanselen@noreply.gitea.com> Co-authored-by: Markus Pesch <markus.pesch@cryptic.systems> Co-committed-by: Markus Pesch <markus.pesch@cryptic.systems>
20 lines
457 B
Smarty
20 lines
457 B
Smarty
{{/* vim: set filetype=mustache: */}}
|
|
|
|
{{/* annotations */}}
|
|
|
|
{{- define "gitea.networkPolicy.annotations" -}}
|
|
{{ include "gitea.annotations" . }}
|
|
{{- if .Values.networkPolicy.annotations }}
|
|
{{ toYaml .Values.networkPolicy.annotations }}
|
|
{{- end }}
|
|
{{- end }}
|
|
|
|
{{/* labels */}}
|
|
|
|
{{- define "gitea.networkPolicy.labels" -}}
|
|
{{ include "gitea.labels" . }}
|
|
{{- if .Values.networkPolicy.labels }}
|
|
{{ toYaml .Values.networkPolicy.labels }}
|
|
{{- end }}
|
|
{{- end }}
|