Allow custom dnsConfig in helm charts (#1569)

Co-authored-by: Anbraten <anton@ju60.de>
This commit is contained in:
Vitali Quiering 2023-02-01 19:09:58 +01:00 committed by GitHub
parent 7835a632e4
commit c73b1ecf2a
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
4 changed files with 15 additions and 0 deletions

View file

@ -91,3 +91,8 @@ spec:
- name: sock-dir
emptyDir: {}
{{- end }}
{{- with .Values.dnsConfig }}
dnsConfig:
{{- toYaml . | nindent 8 }}
{{- end }}

View file

@ -86,6 +86,8 @@ tolerations: []
affinity: {}
dnsConfig: {}
## Using topology spread constraints, you can ensure that there is at least one agent
## pod for each topology zone, e.g. one per arch for multi-architecture clusters
## or one for each region for geographically distributed cloud-hosted clusters.

View file

@ -79,3 +79,8 @@ spec:
persistentVolumeClaim:
claimName: {{ if .Values.persistentVolume.existingClaim }}{{ .Values.persistentVolume.existingClaim }}{{- else }}{{ template "woodpecker-server.fullname" . }}{{- end }}
{{- end -}}
{{- with .Values.dnsConfig }}
dnsConfig:
{{- toYaml . | nindent 8 }}
{{- end }}

View file

@ -97,3 +97,6 @@ nodeSelector: {}
tolerations: []
affinity: {}
dnsConfig: {}