forked from launchdarkly/ld-relay-helm
-
Notifications
You must be signed in to change notification settings - Fork 0
/
values.yaml
170 lines (149 loc) · 5.33 KB
/
values.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
# Default values for ld-relay.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.
replicaCount: 1
image:
# Use the official LaunchDarkly relay proxy image
repository: launchdarkly/ld-relay
pullPolicy: IfNotPresent
# Overrides the image tag whose default is the chart appVersion.
tag: ""
imagePullSecrets: []
nameOverride: ""
fullnameOverride: ""
serviceAccount:
# Specifies whether a service account should be created
create: true
# Annotations to add to the service account
annotations: {}
# The name of the service account to use.
# If not set and create is true, a name is generated using the fullname template
name: ""
pod:
# Annotations to add to the pod. If provided, will take precedence over podAnnotations
annotations: {}
# Labels to add to the pod.
labels: {}
# Security context applied to the pod. If provided, will take precedence over podSecurityContext
securityContext: {}
# fsGroup: 2000
# Deprecated: Use pod.annotations instead
podAnnotations: {}
# Deprecated: Use pod.securityContext instead
podSecurityContext: {}
# fsGroup: 2000
securityContext: {}
# capabilities:
# drop:
# - ALL
# readOnlyRootFilesystem: true
# runAsNonRoot: true
# runAsUser: 1000
service:
type: ClusterIP
annotations: {}
# service.beta.kubernetes.io/aws-load-balancer-internal: "true"
ports:
# WARN: Do not modify the name of this port mapping. It is referenced by other parts of this configuration
- port: 8030
targetPort: 8030
protocol: TCP
name: api
# Prometheus support requires exposing additional ports
# - port: 8031
# targetPort: 8031
# protocol: TCP
# name: prometheus
ingress:
enabled: false
className: ""
annotations: {}
# kubernetes.io/ingress.class: nginx
# kubernetes.io/tls-acme: "true"
hosts: []
# Exposing the relay allows for access outside the cluster
# - host: api.ld-relay.local
# paths:
# - path: /
# pathType: ImplementationSpecific
# port: 8030
# You may optionally need to expose the Prometheus endpoint as well
# - host: prometheus.ld-relay.local
# paths:
# - path: /
# pathType: ImplementationSpecific
# port: 8031
tls: []
# - secretName: chart-example-tls
# hosts:
# - chart-example.local
resources: {}
# We usually recommend not to specify default resources and to leave this as a conscious
# choice for the user. This also increases chances charts run on environments with little
# resources, such as Minikube. If you do want to specify resources, uncomment the following
# lines, adjust them as necessary, and remove the curly braces after 'resources:'.
# limits:
# cpu: 100m
# memory: 128Mi
# requests:
# cpu: 100m
# memory: 128Mi
autoscaling:
enabled: false
minReplicas: 1
maxReplicas: 100
targetCPUUtilizationPercentage: 80
targetMemoryUtilizationPercentage: 80
nodeSelector: {}
tolerations: []
affinity: {}
relay:
# Specify the relay environment variables here to load them into this chart's ConfigMap directly.
# These environment variables should match the ones documented by the relay proxy at https://github.com/launchdarkly/ld-relay
environment: {}
# LD_ENV_MyEnvironment: your-sdk-key
# USE_REDIS: true
# Use k8s secrets to either set environment variables or to mount secrets as files in the relay container.
secrets: []
# Set environment variables in the relay container with values pulled from k8s secrets by specifying the envName property.
# These environment variables should match the ones documented by the relay proxy at https://github.com/launchdarkly/ld-relay
# - envName: REDIS_PASSWORD
# secretName: relay-proxy
# secretKey: redis-password
#
# Setting the volumePath and volumeName values will mount the specified secret as a file into the container.
# All file paths are stored under /mnt/secrets
# - volumePath: path
# volumeName: name
# secretName: relay-proxy
# secretKey: redis-password
# Specify the relay environment variables here.
envVars: []
# - name: RUNNING_HOST
# valueFrom:
# fieldRef:
# fieldPath: status.hostIP
# Enables mounting a k8s volume onto the relay container.
#
# This configuration option is used to optionally provide access to an
# existing relay proxy configuration file, or to provide access to an offline
# file.
volume:
# config should specify the path to the configuration file, relative to the
# root of the provided volume. If left blank, the relay will be configured
# ONLY using environment variables provided in the above two sections.
config: ~
# offline should specify the path to the offline file, relative to the root
# of the provided volume. If left blank, offline mode will be disabled.
# Setting this file will enable offline mode (by setting the FILE_DATA_SOURCE
# environment variable).
offline: ~
# Provide the volume definition required to access either the config or the
# offline files.
#
# Any type of volume supported by k8s should work in the volume setting.
# Refer to the https://kubernetes.io/docs/concepts/storage/volumes/
# documentation for more information.
definition: {}
# persistentVolumeClaim:
# claimName: ld-relay-pvc