forked from jenkins-x/jx3-pipeline-catalog
-
Notifications
You must be signed in to change notification settings - Fork 0
/
values.yaml
135 lines (119 loc) · 3.11 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
# Default values for your projects.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.
replicaCount: 1
# Add annotations to the pods
podAnnotations: {}
# Add labels to the pods
podsLabels: {}
# Add labels to the deployment
deploymentLabels: {}
image:
repository: draft
tag: dev
pullPolicy: IfNotPresent
# optional list of image pull secrets to use to pull images
jx:
# optional image pull secrets
imagePullSecrets: []
# whether to create a Release CRD when installing charts with Release CRDs included
releaseCRD: true
# define environment variables here as a map of key: value
env:
# enable this flag to use knative serve to deploy the app
knativeDeploy: false
# HorizontalPodAutoscaler
hpa:
enabled: false
minReplicas: 2
maxReplicas: 6
cpuTargetAverageUtilization: 80
memoryTargetAverageUtilization: 80
# Add labels to the HPA
labels: {}
# Canary deployments
# If enabled, Istio and Flagger need to be installed in the cluster
canary:
enabled: false
progressDeadlineSeconds: 60
analysis:
interval: "1m"
threshold: 5
maxWeight: 60
stepWeight: 20
# WARNING: Canary deployments will fail and rollback if there is no traffic that will generate the below specified metrics.
metrics:
latency:
threshold: 500
interval: "1m"
# The host is using Istio Gateway or the underlying ingress mechanism
# This value is defaulted from the environments jx-requirements.yml ingress configuration
host: ""
# Add labels to the canary
labels: {}
# Add labels to the canary gateway
gatewayLabels: {}
service:
name: REPLACE_ME_APP_NAME
type: ClusterIP
externalPort: 80
internalPort: 8080
annotations: {}
# Add labels to the service
labels: {}
resources:
limits:
cpu: 400m
memory: 256Mi
requests:
cpu: 0.1
memory: 128Mi
probePath: /
livenessProbe:
initialDelaySeconds: 60
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 1
# Optional distinct liveness probe path, if empty the probePath is used
probePath: ""
readinessProbe:
failureThreshold: 1
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 1
# Optional distinct readiness probe path, if empty the probePath is used
probePath: ""
# custom ingress annotations on this service
ingress:
annotations: {}
# defaults to nginx if no other ingress class annotation specified
classAnnotation: ""
# Add labels to the ingress
labels: {}
# ingress path type
pathType: ImplementationSpecific
serviceAccount:
enabled: true
name: ""
annotations: {}
# iam.gke.io/gcp-service-account: my-sa-in-gke
# Add labels to the SA
labels: {}
# my-custom-label: value
# values we use from the `jx-requirements.yml` file if we are using helmfile and helm 3
jxRequirements:
ingress:
# shared ingress annotations on all services
annotations: {}
# kubernetes.io/ingress.class: nginx
apiVersion: "networking.k8s.io/v1"
# the domain for hosts
domain: ""
externalDNS: false
namespaceSubDomain: -jx.
serviceType: ""
tls:
email: ""
enabled: false
production: false
secretName: ""