Re-enable ability to select Nodeport for service setup #14854 (#16624)

This commit is contained in:
George Karr
2024-02-06 14:49:13 -06:00
committed by GitHub
parent acd8d91350
commit 3e1b5dc16e
3 changed files with 12 additions and 4 deletions
+1 -1
View File
@@ -4,7 +4,7 @@ name: fleet
keywords:
- fleet
- osquery
version: v6.0.1
version: v6.0.2
home: https://github.com/fleetdm/fleet
sources:
- https://github.com/fleetdm/fleet.git
+8 -3
View File
@@ -9,6 +9,9 @@ metadata:
name: fleet
namespace: {{ .Release.Namespace }}
spec:
{{- if .Values.gke.ingress.useGKEIngress }}
type: NodePort
{{- end }}
selector:
app: fleet
chart: fleet
@@ -17,6 +20,8 @@ spec:
ports:
- name: fleet
port: {{ .Values.fleet.listenPort }}
{{- if .Values.gke.ingress.useGKEIngress }}
type: NodePort
{{- end }}
{{- if .Values.gke.ingress.useGKEIngress }}
{{- if .Values.gke.ingress.nodePort }}
nodePort: {{ .Values.gke.ingress.nodePort }}
{{- end }}
{{- end }}
+3
View File
@@ -191,6 +191,9 @@ gke:
# The GKE Ingress requires a few changes that other ingress controllers don't
ingress:
useManagedCertificate: false
useGKEIngress: false
# 0 to allow the nodeport to be automatically selected, otherwise allowed range (30000-32767)
nodePort: 0
# Workload Identity allows the K8s service account to assume the IAM permissions of a GCP service account
workloadIdentityEmail: ""