You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Go to the following for an example of a Kubernetes manifest that you can use to configure Harness Delegate and the Helm chart default `values.yaml` file.
For the latest references, see the most up-to-date [Helm chart default `values.yaml` file example found in our repository](https://github.com/harness/delegate-helm-chart/blob/main/harness-delegate-ng/values.yaml).
256
258
257
259
```yaml
258
-
# Default configuration values for the Harness Delegate NextGen.
260
+
# Default values for delegate-ng.
259
261
# This is a YAML-formatted file.
260
262
# Declare variables to be passed into your templates.
261
263
262
264
image:
263
265
pullPolicy: Always
266
+
# Uncomment below lines to use a custom registry + repository, a different repository or a different tag, this will override the delegateDockerImage
267
+
# registry: null
268
+
# repository: null
269
+
# tag: null
264
270
265
271
fullnameOverride: ""
266
272
273
+
mTLS:
274
+
secretName: ""
275
+
267
276
serviceAccount:
268
277
# Specifies whether a service account should be created.
269
278
create: true
@@ -274,7 +283,7 @@ serviceAccount:
274
283
name: ""
275
284
276
285
service:
277
-
# type: ClusterIP
286
+
# type: ClusterIP
278
287
port: 8080
279
288
280
289
# Edit this if you want to enable horizontal pod autoscaling.
# Annotations for delegate deployment; Prometheus is added by default.
311
+
commonAnnotations: {} # Annotations that will be applied to all resources
312
+
delegateAnnotations: {} # Annotations that will be applied to both pod and deployment spec for Delegate
313
+
# Annotations for delegate deployment, prometheus is added by default
303
314
annotations:
304
315
prometheus.io/scrape: "true"
305
316
prometheus.io/port: "3460"
306
317
prometheus.io/path: "/api/metrics"
307
318
319
+
commonLabels: {} # Labels that will be applied to all resources
320
+
delegatePodLabels: {} # Labels that will be applied to pod spec
321
+
delegateLabels: {} # Labels that will be applied to both deployment and pod spec for Delegate
322
+
308
323
imagePullSecret: ""
309
324
310
-
# Endpoint that will point to the Harness platform. For accessing SaaS platform use the default value.
325
+
# Endpoint that will point to the Harness platform. For accessing the SaaS platform, use the default value.
311
326
managerEndpoint: https://app.harness.io
312
327
313
328
# If socket connection is not supported, set this flag to true to poll tasks using REST API calls.
@@ -342,7 +357,24 @@ replicas: 1
342
357
# possible due to custom volumes or mounts that can only be attached to a single pod.
343
358
deploymentStrategy: "RollingUpdate"
344
359
345
-
# Resource limits of the container running the delegate image in Kubernetes.
360
+
# Rolling update configuration (only applies when deploymentStrategy is "RollingUpdate").
361
+
# By default, these are not set so Kubernetes uses its own defaults (currently 25%).
362
+
# Uncomment and set if you want to override the defaults. You may use integers or percentage strings (e.g., "25%")
363
+
# rollingUpdate:
364
+
# # Maximum number of pods that can be created above the desired replica count during updates
365
+
# maxSurge: "25%"
366
+
# # Maximum number of pods that can be unavailable during the update process
367
+
# maxUnavailable: "25%"
368
+
369
+
# Resource limits of container running delegate image in kubernetes
370
+
# If you want to set custom resource limits, uncomment the below line and set the values for cpu and memory request/limit
371
+
# resources:
372
+
# limits:
373
+
# cpu: 1
374
+
# memory: 2048Mi
375
+
# requests:
376
+
# cpu: 1
377
+
# memory: 2048Mi
346
378
cpu: 1
347
379
memory: 2048
348
380
@@ -357,15 +389,31 @@ javaOpts: "-Xms64M"
357
389
upgrader:
358
390
enabled: true
359
391
upgraderDockerImage: "harness/upgrader:latest"
392
+
registryMirror: ""
393
+
image:
394
+
pullPolicy: Always
395
+
# Uncomment below lines to use a custom registry + repository, a different repository or a different tag, this will override the upgraderDockerImage
396
+
# registry: null
397
+
# repository: null
398
+
# tag: null
399
+
400
+
# Schedule for the upgrader cronjob (cron format)
401
+
schedule: "0 */1 * * *"
402
+
403
+
imagePullSecret: ""
404
+
360
405
cronJobServiceAccountName: "upgrader-cronjob-sa"
361
-
# Use an existing Secret that stores the UPGRADER_TOKEN key instead of creating a new one. The value should be set with the `UPGRADER_TOKEN` key inside the secret.
406
+
# Use an existing Secret which stores the UPGRADER_TOKEN key instead of creating a new one. The value should be set with the `UPGRADER_TOKEN` key inside the secret.
362
407
## The use of external secrets allows you to manage credentials from external tools like Vault, 1Password, SealedSecrets, among others.
363
408
## If set, this parameter takes precedence over "upgraderToken".
364
409
## Recommendations:
365
410
## - Use different Secrets names for `existingUpgraderToken` and `existingDelegateToken`.
366
411
## - Do not use Secrets managed by other Helm deployments.
367
412
existingUpgraderToken: ""
368
413
414
+
# Set security context for upgrader
415
+
securityContext:
416
+
369
417
# This field is DEPRECATED, DON'T OVERRIDE/USE THIS!!
370
418
# To set root/non-root access and other security context, use the delegateSecurityContext field below.
371
419
# Not removing this field to maintain backward compatibility.
0 commit comments