Skip to content

Commit

Permalink
control-service: update ingress (#2853)
Browse files Browse the repository at this point in the history
Why
Currently, there is no way to exclude the user interface (UI) from the
Ingress configuration.

What
To address this issue, we introduced a new check within the Ingress
configuration. This check allows for determining whether the UI is
enabled or not

Testing done:
helm template

Signed-off-by: Miroslav Ivanov [email protected]

Signed-off-by: Miroslav Ivanov [email protected]
  • Loading branch information
mivanov1988 authored Oct 31, 2023
1 parent 7de96d9 commit dd34c06
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 0 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -11,17 +11,22 @@ metadata:
annotations: {{- toYaml .Values.ingress.annotations | nindent 4 }}
apiVersion: networking.k8s.io/v1
spec:
{{- if .Values.ingress.className }}
ingressClassName: {{ .Values.ingress.className }}
{{- end }}
rules:
- host: {{ .Values.ingress.host | quote }}
http:
paths:
{{- if .Values.operationsUi.enabled }}
- path: {{ .Values.ingress.path | default "/" }}
pathType: "ImplementationSpecific"
backend:
service:
name: {{ .Release.Name }}-ui
port:
number: 8091
{{- end }}
- path: {{ .Values.ingress.path | default "/data-jobs" }}
pathType: "ImplementationSpecific"
backend:
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -115,6 +115,8 @@ ingress:
## we use community Nginx controller which supports SNI, thus a signle IP could terminate all connections.
## https://github.com/kubernetes/ingress-nginx/
tls_secret: ""
## It is used to associate an Ingress resource with a specific Ingress controller or implementation.
className: ""

# Embedded server settings
server:
Expand Down

0 comments on commit dd34c06

Please sign in to comment.