-
Notifications
You must be signed in to change notification settings - Fork 18
/
values.yaml
288 lines (260 loc) · 9.42 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
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
## edp-install configuration
## Ref: https://github.com/epam/edp-install
##
##
global:
# -- EDP version
version: "3.6.0"
# -- platform type that can be "kubernetes" or "openshift"
platform: "kubernetes"
# -- a cluster DNS wildcard name
dnsWildCard:
# -- Can be gerrit, github or gitlab. By default: github
gitProvider: github
# -- Gerrit SSH node port
# gerritSSHPort: "22"
# Define the Image Registry that will be used in Pipelines.
# This section is optional, and users can configure the registry within the EDP Portal user interface.
#
# Platform supports several types of registries, such as 'ecr', 'harbor', 'dockerhub' and 'openshift'.
# 'openshift' registry is available only in case if platform is deployed on the OpenShift cluster and the variable global.platform is set to 'openshift'
#
# Below is an example of endpoint values for each registry type:
# type: | url
# =============================
# ecr | <aws_account_id>.dkr.ecr.<aws_region>.amazonaws.com
# harbor | <registry.example.com>
# dockerhub | 'docker.io'
# openshift | <image-registry.openshift-image-registry.svc:5000>
#
# For example to integrate platform with dockerhub and publish image under 'my_user' account:
# dockerRegistry:
# type: "dockerhub"
# url: "docker.io"
# space: "my_user"
# As a result all image artifacts are published under https://hub.docker.com/repository/docker/my_user
dockerRegistry:
type: ""
url: ""
space: ""
# -- AWS Region, e.g. "eu-central-1"
awsRegion:
# -- Enable SSO for EDP components. Required keycloak-operator deployment. Default: false
sso:
enabled: false
# -- Keycloak URL
keycloakUrl: https://keycloak.example.com
# -- Administrators of your tenant
admins:
- "stub_user_one@example.com"
# -- Developers of your tenant
developers:
- "stub_user_one@example.com"
- "stub_user_two@example.com"
# Configure External Secrets Operator to provision secrets for Platform and/or EDP
# https://external-secrets.io/latest/provider-aws-secrets-manager/
externalSecrets:
# -- Configure External Secrets for EDP platform. Deploy SecretStore
enabled: false
secretProvider:
aws:
# -- Use AWS as a Secret Provider. Can be ParameterStore or SecretsManager
service: ParameterStore
# -- IAM Role to be used for Accessing AWS either Parameter Store or Secret Manager. Format: arn:aws:iam::<AWS_ACCOUNT_ID>:role/<AWS_IAM_ROLE_NAME>
role:
# -- AWS Region where secrets are stored, e.g. eu-central-1
region: eu-central-1
# When installing EDP, three secrets must be created: super-admin-db, db-admin-console, keycloak and kaniko-docker-config
# see https://epam.github.io/edp-install/operator-guide/install-edp/
# manageEDPInstallSecrets creates required secrets using ExternalSecretOperator
# Ensure external secret source is configured properly
# -- Create necessary secrets for EDP installation, using External Secret Operator
manageEDPInstallSecrets: true
# -- Value name in AWS ParameterStore or AWS SecretsManager. Used when manageEDPInstallSecrets is true
manageEDPInstallSecretsName: /edp/deploy-secrets
annotations: {}
codebase-operator:
enabled: true
# image:
# repository: epamedp/codebase-operator
# tag:
# envs:
# - name: RECONCILATION_PERIOD
# value: "360" # The value should be typed in minutes
# # Maximum number of parallel reconciliation codebasebranches
# - name: CODEBASE_BRANCH_MAX_CONCURRENT_RECONCILES
# value: 3
# jira:
# integration: false
# name: "jira"
# apiUrl: "https://jiraeu-api.example.com"
# rootUrl: "https://jiraeu.example.com"
# credentialName: "ci-jira"
cd-pipeline-operator:
enabled: true
# image:
# repository: epamedp/cd-pipeline-operator
# tag:
# -- defines the type of the tenant engine that can be "none", "kiosk" or "capsule"
tenancyEngine: "none"
gerrit-operator:
enabled: false
# image:
# repository: epamedp/gerrit-operator
# tag:
# gerrit:
# deploy: true
# name: "gerrit"
# image: "openfrontier/gerrit"
# version:
# imagePullSecrets:
# storage:
# size: 1Gi
# class: gp2
edp-headlamp:
enabled: true
config:
oidc:
enabled: false
clientID: "kubernetes"
clientSecretName: "keycloak-client-headlamp-secret"
clientSecretKey: "clientSecret"
issuerRealm: "openshift"
# image:
# repository: epamedp/edp-headlamp
# tag:
edp-tekton:
enabled: true
dashboard:
# -- Deploy EDP Dashboard as a part of pipeline library when true. Default: true
enabled: true
# -- Make it possible to use openshift as OIDC provider to hide tekton-dashboard.
# -- Only for openshift deploy scenario,
# -- For EKS scenario - uncomment dashboard.ingress.annotations block and
# -- set the value of the oauth2_proxy.enable to true
# -- More details:
# -- https://epam.github.io/edp-install/operator-guide/oauth2-proxy/?h=#enable-oauth2-proxy-on-tekton-dashboard
openshift_proxy:
# -- Enable oauth-proxy to include authorization layer on tekton-dashboard. Default: flase
enabled: false
ingress:
# -- Annotations for Ingress resource
annotations: {}
# -- Uncomment it to enable tekton-dashboard OIDC on EKS cluster
# nginx.ingress.kubernetes.io/auth-signin='https://<oauth-ingress-host>/oauth2/start?rd=https://$host$request_uri'
# nginx.ingress.kubernetes.io/auth-url='http://oauth2-proxy.edp.svc.cluster.local:8080/oauth2/auth'
ctLint:
# -- This block make possible to modify ct-lint configuration. It setup ct-lint parameters: "--config", "--chart-yaml-schema" and "--lint-conf".
# -- Config block.
validateMaintainers: false # -- true or false
# -- Chart schema block.
# -- Example parameters: https://github.com/helm/chart-testing/blob/main/etc/chart_schema.yaml
# chartSchema: |
# name: str()
# home: str()
# version: str()
# type: str()
# -- Lint-conf block.
# -- Example parameters: https://github.com/helm/chart-testing/blob/main/etc/lintconf.yaml
# lintconf: |
# ---
# rules:
# braces:
# min-spaces-inside: 0
# max-spaces-inside: 0
# Proxy configuration section
oauth2_proxy:
# oauth2-proxy requires keycloak to be configured properly before deployment
# you can set enable: true, when your platform is deployed and keycloak is
# configured.
# -- Install oauth2-proxy as a part of EDP deployment. Default: false
enabled: false
image:
# -- oauth2-proxy image repository
repository: quay.io/oauth2-proxy/oauth2-proxy
# -- oauth2-proxy image tag
tag: v7.4.0
# Create a cookie-secret with the following command
# openssl rand -base64 32 | head -c 32 | base64
# Use an existing secret for OAuth2 cookie-secret
existingSecret:
# -- Secret name which stores cookie-secret
secretName: oauth2-proxy-cookie-secret
# -- Secret key which stores cookie-secret
secretKey: cookie-secret
extraEnv: []
extraArgs: {}
# -- Additional volumes to be added to the oauth2-proxy pod
extraVolumes: []
# - name: custom-ca
# secret:
# defaultMode: 420
# secretName: custom-ca
# -- Additional volumeMounts to be added to the oauth2-proxy container
extraVolumeMounts: []
# - name: custom-ca
# mountPath: /etc/ssl/certs/CA.crt
# readOnly: true
# subPath: CA.crt
ingress:
annotations: {}
# -- pathType is only for k8s >= 1.1=
pathType: Prefix
# -- For Kubernetes >= 1.18 you should specify the ingress-controller via the field ingressClassName
# -- See https://kubernetes.io/blog/2020/04/02/improvements-to-the-ingress-api-in-kubernetes-1.18/#specifying-the-class-of-an-ingress
# ingressClassName: nginx
tls: []
# - secretName: chart-example-tls
# hosts:
# - chart-example.local
# define EDPComponents, more details: https://github.com/epam/edp-component-operator/
EDPComponents: {}
# - prometheus:
# url: https://ingress-prometheus.example.com
# visible: true
# icon: icon_in_base64
# - kibana:
# url: https://ingress-kibana.example.com
# visible: false
# icon: icon_in_base64
# - another_tool:
# url: https://ingress-anothertool.example.com
# visible: true
# icon: icon_in_base64
# -- Array of extra K8s manifests to deploy
extraObjects: []
# - apiVersion: external-secrets.io/v1beta1
# kind: ExternalSecret
# metadata:
# name: example-secret-1
# spec:
# data:
# - remoteRef:
# key: /edp/deploy-secrets
# property: example-secret-1.username
# secretKey: username
# - remoteRef:
# key: /edp/deploy-secrets
# property: example-secret-1.password
# secretKey: password
# secretStoreRef:
# kind: SecretStore
# name: example-parameterstore
# - |
# apiVersion: external-secrets.io/v1beta1
# kind: ExternalSecret
# metadata:
# name: example-secret-2
# spec:
# data:
# - remoteRef:
# key: /edp/deploy-secrets
# property: example-secret-2.username
# secretKey: username
# - remoteRef:
# key: /edp/deploy-secrets
# property: example-secret-2.password
# secretKey: password
# secretStoreRef:
# kind: SecretStore
# name: example-parameterstore