ref(argo-cd): using default value for gateway name

Signed-off-by: Tristan Duverger <tristan.duverger@gmail.com>
This commit is contained in:
Tristan Duverger 2024-10-04 10:55:11 +02:00 committed by Tristan Duverger
parent a8d4216c23
commit 44377b3664
3 changed files with 5 additions and 3 deletions

View file

@ -19,7 +19,7 @@ spec:
parentRefs:
- group: gateway.networking.k8s.io
kind: Gateway
name: {{ tpl .Values.server.gateway.name . }}
name: {{ .Values.server.gateway.name | default (include "argo-cd.server.fullname" .) }}
{{- with .Values.server.gateway.httpRoute.gatewaySection }}
sectionName: {{ . }}
{{- end }}

View file

@ -2,7 +2,7 @@
kind: Gateway
apiVersion: gateway.networking.k8s.io/v1
metadata:
name: {{ tpl .Values.server.gateway.name . }}
name: {{ .Values.server.gateway.name | default (include "argo-cd.server.fullname" .) }}
namespace: {{ .Release.Namespace | quote }}
labels:
{{- include "argo-cd.labels" (dict "context" . "component" .Values.server.name "name" .Values.server.name) | nindent 4 }}

View file

@ -2157,7 +2157,9 @@ server:
# -- enable a gateway resource for ArgoCD
## Note: you can already have an existing Gateway and just wanted to add a route and backend policy to that Gateway, let false in that case
enabled: false
name: '{{ include "argo-cd.server.fullname" . }}'
# -- Name of the new gateway
# @default -- `""` (calculated with template "argo-cd.server.fullname") (See [values.yaml])
name: ""
# -- Specific implementation for gateway controller. Only `None` and `gke` are supported.
## With `None`, the gateway is supposed to already exist and no specific object will be created
## Additional configuration might be required in related configuration sections for `gke`