Skip to content

Commit

Permalink
195: allow user to choose if they want a Kibana ingress to be deployed
Browse files Browse the repository at this point in the history
also removes a superfluous boolean controlling if Tekton gets deployed
  • Loading branch information
Pavlos Tzianos authored and ptzianos committed Jun 5, 2024
1 parent 0f1d009 commit faaf0fb
Show file tree
Hide file tree
Showing 3 changed files with 2 additions and 4 deletions.
2 changes: 1 addition & 1 deletion deploy/dracon/chart/templates/kb-ingress.yaml
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
{{ if .Values.kibana.enabled }}
{{ if .Values.kibana.ingress.enabled }}
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
Expand Down
3 changes: 0 additions & 3 deletions deploy/dracon/chart/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -48,9 +48,6 @@ postgresql:
postgresPassword: ""
fullnameOverride: ""

tekton:
enabled: true

# this section controls aspects of managing a database used to store enrichments
# the database should use the Postgres dialect.
enrichmentDB:
Expand Down
1 change: 1 addition & 0 deletions deploy/dracon/values/dev.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,7 @@ kibana:
enabled: true
version: 8.3.2
ingress:
enabled: true
className: nginx
host: kibana.dracon.localhost
tlsEnabled: false
Expand Down

0 comments on commit faaf0fb

Please sign in to comment.