-
Notifications
You must be signed in to change notification settings - Fork 25
/
Copy pathvalues.yaml
127 lines (107 loc) · 3.77 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
# Default values for jetstack-agent.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.
# -- default replicas, do not scale up
replicaCount: 1
image:
# -- Default to Open Source image repository
repository: quay.io/jetstack/preflight
# -- Defaults to only pull if not already present
pullPolicy: IfNotPresent
# -- Overrides the image tag whose default is the chart appVersion
tag: "v0.1.43"
# -- Specify image pull credentials if using a prviate registry
imagePullSecrets: []
# -- Helm default setting to override release name, leave blank
nameOverride: ""
# -- Helm default setting, use this to shorten install name
fullnameOverride: ""
serviceAccount:
# -- Specifies whether a service account should be created
# @default true
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: ""
podAnnotations: {}
podSecurityContext: {}
# fsGroup: 2000
securityContext:
capabilities:
drop:
- ALL
readOnlyRootFilesystem: true
runAsNonRoot: true
runAsUser: 1000
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:'.
requests:
memory: 200Mi
cpu: 200m
limits:
memory: 500Mi
cpu: 500m
nodeSelector: {}
tolerations: []
affinity: {}
# -- Additional volumes to add to the jetstack-agent pod.
volumes: []
# -- Additional volume mounts to add to the jetstack-agent container.
volumeMounts: []
# -- Override the jetstack-agent entrypoint with specified command.
command: []
# -- Add additional arguments to the default `agent` command.
extraArgs: []
# -- Authentication section for the agent
authentication:
# -- Reccomend that you do not use this and instead creat the credential secret outside of helm
createSecret: false
# -- Type can be "file"/"token" determining how the agent should authenticate the to the backend
type: file
# -- Name of the secret containing agent credentials.json
secretName: agent-credentials
# -- Key name in secret
secretKey: "credentials.json"
# -- Base64 encoded value from Jetstack Secure Dashboard - only required when createSecret is true
secretValue: ""
# -- Configuration section for the Jetstack Agent itself
config:
# -- Overrides the server if using a proxy between agent and Jetstack Secure
server: "https://platform.jetstack.io"
# -- REQUIRED - Your Jetstack Secure Organisation Name
organisation: ""
# -- REQUIRED - Your Jetstack Secure Cluster Name
cluster: ""
# -- Send data back to the platform every minute unless changed
period: "0h1m0s"
# -- Configure data that is gathered from your cluster, for full details see https://platform.jetstack.io/documentation/configuration/jetstack-agent/configuration
dataGatherers:
# -- Use the standard full set of data gatherers
default: true
# -- A list of data gatherers to limit agent scope
custom: []
# Full list that makes up the default role
# - node
# - secret
# - cert-manager
# - googlecas
# - awspca
# - webhook
# - openshift
# - istio
# - venafienhancedissuer
# -- Provide an Override to allow completely custom agent configuration
override:
# -- Override disabled by default
enabled: false
# -- Embed the agent configuration here in the chart values
config:
# -- Sepcify ConfigMap details to load config from existing ConfigMap
configmap:
name:
key: