diff --git a/README.md b/README.md index ec394b84a..52723a128 100644 --- a/README.md +++ b/README.md @@ -75,7 +75,7 @@ helm uninstall my-release The following table lists the configurable parameters of the Harbor chart and the default values. -| Parameter | Description | Default | +| Parameter | Description | Default | |-----------------------------------------------------------------------| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------- | | **Expose** | | | | `expose.type` | How to expose the service: `ingress`, `clusterIP`, `nodePort` or `loadBalancer`, other values will be ignored and the creation of service will be skipped. | `ingress` | @@ -201,6 +201,7 @@ The following table lists the configurable parameters of the Harbor chart and th | `nginx.topologySpreadConstraints` | Constraints that define how Pods are spread across failure-domains like regions or availability zones | `[]` | | `nginx.podAnnotations` | Annotations to add to the nginx pod | `{}` | | `nginx.priorityClassName` | The priority class to run the pod as | | +| `nginx.lifecycle` | Container lifecycle | `{}` | | **Portal** | | | | `portal.image.repository` | Repository for portal image | `goharbor/harbor-portal` | | `portal.image.tag` | Tag for portal image | `dev` | @@ -213,9 +214,9 @@ The following table lists the configurable parameters of the Harbor chart and th | `portal.affinity` | Node/Pod affinities | `{}` | | `portal.topologySpreadConstraints` | Constraints that define how Pods are spread across failure-domains like regions or availability zones | `[]` | | `portal.podAnnotations` | Annotations to add to the portal pod | `{}` | -| `portal.serviceAnnotations` | Annotations to add to the portal service | `{}` | +| `portal.serviceAnnotations` | Annotations to add to the portal service | `{}` | | `portal.priorityClassName` | The priority class to run the pod as | | -| `portal.initContainers` | Init containers to be run before the controller's container starts. | `[]` | +| `portal.initContainers` | Init containers to be run before the controller's container starts. | `[]` | | **Core** | | | | `core.image.repository` | Repository for Harbor core image | `goharbor/harbor-core` | | `core.image.tag` | Tag for Harbor core image | `dev` | @@ -230,8 +231,8 @@ The following table lists the configurable parameters of the Harbor chart and th | `core.topologySpreadConstraints` | Constraints that define how Pods are spread across failure-domains like regions or availability zones | `[]` | | `core.podAnnotations` | Annotations to add to the core pod | `{}` | | `core.serviceAnnotations` | Annotations to add to the core service | `{}` | -| `core.configureUserSettings` | A JSON string to set in the environment variable `CONFIG_OVERWRITE_JSON` to configure user settings. See the [official docs](https://goharbor.io/docs/latest/install-config/configure-user-settings-cli/#configure-users-settings-using-an-environment-variable). | | -| `core.quotaUpdateProvider` | The provider for updating project quota(usage), there are 2 options, redis or db. By default it is implemented by db but you can configure it to redis which can improve the performance of high concurrent pushing to the same project, and reduce the database connections spike and occupies. Using redis will bring up some delay for quota usage updation for display, so only suggest switch provider to redis if you were ran into the db connections spike around the scenario of high concurrent pushing to same project, no improvment for other scenes. | `db` | +| `core.configureUserSettings` | A JSON string to set in the environment variable `CONFIG_OVERWRITE_JSON` to configure user settings. See the [official docs](https://goharbor.io/docs/latest/install-config/configure-user-settings-cli/#configure-users-settings-using-an-environment-variable). | | +| `core.quotaUpdateProvider` | The provider for updating project quota(usage), there are 2 options, redis or db. By default it is implemented by db but you can configure it to redis which can improve the performance of high concurrent pushing to the same project, and reduce the database connections spike and occupies. Using redis will bring up some delay for quota usage updation for display, so only suggest switch provider to redis if you were ran into the db connections spike around the scenario of high concurrent pushing to same project, no improvment for other scenes. | `db` | | `core.secret` | Secret is used when core server communicates with other components. If a secret key is not specified, Helm will generate one. Must be a string of 16 chars. | | | `core.secretName` | Fill the name of a kubernetes secret if you want to use your own TLS certificate and private key for token encryption/decryption. The secret must contain keys named: `tls.crt` - the certificate and `tls.key` - the private key. The default key pair will be used if it isn't set | | | `core.tokenKey` | PEM-formatted RSA private key used to sign service tokens. Only used if `core.secretName` is unset. If set, `core.tokenCert` MUST also be set. | | @@ -240,8 +241,9 @@ The following table lists the configurable parameters of the Harbor chart and th | `core.priorityClassName` | The priority class to run the pod as | | | `core.artifactPullAsyncFlushDuration` | The time duration for async update artifact pull_time and repository pull_count | | | `core.gdpr.deleteUser` | Enable GDPR compliant user delete | `false` | -| `core.gdpr.auditLogsCompliant` | Enable GDPR compliant for audit logs by changing username to its CRC32 value if that user was deleted from the system | `false` | -| `core.initContainers` | Init containers to be run before the controller's container starts. | `[]` | +| `core.gdpr.auditLogsCompliant` | Enable GDPR compliant for audit logs by changing username to its CRC32 value if that user was deleted from the system | `false` | +| `core.initContainers` | Init containers to be run before the controller's container starts. | `[]` | +| `core.lifecycle` | Container lifecycle | `{}` | | **Jobservice** | | | | `jobservice.image.repository` | Repository for jobservice image | `goharbor/harbor-jobservice` | | `jobservice.image.tag` | Tag for jobservice image | `dev` | @@ -252,8 +254,8 @@ The following table lists the configurable parameters of the Harbor chart and th | `jobservice.loggerSweeperDuration` | The jobLogger sweeper duration in days (ignored if `jobLoggers` is set to `stdout`) | `14` | | `jobservice.notification.webhook_job_max_retry` | The maximum retry of webhook sending notifications | `3` | | `jobservice.notification.webhook_job_http_client_timeout` | The http client timeout value of webhook sending notifications | `3` | -| `jobservice.reaper.max_update_hours` | the max time to wait for a task to finish, if unfinished after max_update_hours, the task will be mark as error, but the task will continue to run, default value is 24 | `24` | -| `jobservice.reaper.max_dangling_hours` | the max time for execution in running state without new task created | `168` | +| `jobservice.reaper.max_update_hours` | the max time to wait for a task to finish, if unfinished after max_update_hours, the task will be mark as error, but the task will continue to run, default value is 24 | `24` | +| `jobservice.reaper.max_dangling_hours` | the max time for execution in running state without new task created | `168` | | `jobservice.resources` | The [resources] to allocate for container | undefined | | `jobservice.automountServiceAccountToken` | Mount serviceAccountToken? | `false` | | `jobservice.nodeSelector` | Node labels for pod assignment | `{}` | @@ -263,14 +265,17 @@ The following table lists the configurable parameters of the Harbor chart and th | `jobservice.podAnnotations` | Annotations to add to the jobservice pod | `{}` | | `jobservice.priorityClassName` | The priority class to run the pod as | | | `jobservice.secret` | Secret is used when job service communicates with other components. If a secret key is not specified, Helm will generate one. Must be a string of 16 chars. | | -| `jobservice.initContainers` | Init containers to be run before the controller's container starts. | `[]` | +| `jobservice.initContainers` | Init containers to be run before the controller's container starts. | `[]` | +| `jobservice.lifecycle` | Container lifecycle | `{}` | | **Registry** | | | | `registry.registry.image.repository` | Repository for registry image | `goharbor/registry-photon` | | `registry.registry.image.tag` | Tag for registry image | `dev` | | `registry.registry.resources` | The [resources] to allocate for container | undefined | +| `registry.registry.lifecycle` | Container lifecycle | `{}` | | `registry.controller.image.repository` | Repository for registry controller image | `goharbor/harbor-registryctl` | | `registry.controller.image.tag` | Tag for registry controller image | `dev` | | `registry.controller.resources` | The [resources] to allocate for container | undefined | +| `registry.controller.lifecycle` | Container lifecycle | `{}` | | `registry.replicas` | The replica count | `1` | | `registry.revisionHistoryLimit` | The revision history limit | `10` | | `registry.nodeSelector` | Node labels for pod assignment | `{}` | @@ -282,16 +287,16 @@ The following table lists the configurable parameters of the Harbor chart and th | `registry.podAnnotations` | Annotations to add to the registry pod | `{}` | | `registry.priorityClassName` | The priority class to run the pod as | | | `registry.secret` | Secret is used to secure the upload state from client and registry storage backend. See [official docs](https://github.com/docker/distribution/blob/master/docs/configuration.md#http). If a secret key is not specified, Helm will generate one. Must be a string of 16 chars. | | -| `registry.credentials.username` | The username that harbor core uses internally to access the registry instance. Together with the `registry.credentials.password`, a htpasswd is created. This is an alternative to providing `registry.credentials.htpasswdString`. For more details see [official docs](https://github.com/docker/distribution/blob/master/docs/configuration.md#htpasswd). | `harbor_registry_user` | -| `registry.credentials.password` | The password that harbor core uses internally to access the registry instance. Together with the `registry.credentials.username`, a htpasswd is created. This is an alternative to providing `registry.credentials.htpasswdString`. For more details see [official docs](https://github.com/docker/distribution/blob/master/docs/configuration.md#htpasswd). It is suggested you update this value before installation. | `harbor_registry_password` | -| `registry.credentials.existingSecret` | An existing secret containing the password for accessing the registry instance, which is hosted by htpasswd auth mode. More details see [official docs](https://github.com/docker/distribution/blob/master/docs/configuration.md#htpasswd). The key must be `REGISTRY_PASSWD` | `""` | +| `registry.credentials.username` | The username that harbor core uses internally to access the registry instance. Together with the `registry.credentials.password`, a htpasswd is created. This is an alternative to providing `registry.credentials.htpasswdString`. For more details see [official docs](https://github.com/docker/distribution/blob/master/docs/configuration.md#htpasswd). | `harbor_registry_user` | +| `registry.credentials.password` | The password that harbor core uses internally to access the registry instance. Together with the `registry.credentials.username`, a htpasswd is created. This is an alternative to providing `registry.credentials.htpasswdString`. For more details see [official docs](https://github.com/docker/distribution/blob/master/docs/configuration.md#htpasswd). It is suggested you update this value before installation. | `harbor_registry_password` | +| `registry.credentials.existingSecret` | An existing secret containing the password for accessing the registry instance, which is hosted by htpasswd auth mode. More details see [official docs](https://github.com/docker/distribution/blob/master/docs/configuration.md#htpasswd). The key must be `REGISTRY_PASSWD` | `""` | | `registry.credentials.htpasswdString` | Login and password in htpasswd string format. Excludes `registry.credentials.username` and `registry.credentials.password`. May come in handy when integrating with tools like argocd or flux. This allows the same line to be generated each time the template is rendered, instead of the `htpasswd` function from helm, which generates different lines each time because of the salt. | undefined | | `registry.relativeurls` | If true, the registry returns relative URLs in Location headers. The client is responsible for resolving the correct URL. Needed if harbor is behind a reverse proxy | `false` | | `registry.upload_purging.enabled` | If true, enable purge _upload directories | `true` | | `registry.upload_purging.age` | Remove files in _upload directories which exist for a period of time, default is one week. | `168h` | | `registry.upload_purging.interval` | The interval of the purge operations | `24h` | | `registry.upload_purging.dryrun` | If true, enable dryrun for purging _upload, default false | `false` | -| `registry.initContainers` | Init containers to be run before the controller's container starts. | `[]` | +| `registry.initContainers` | Init containers to be run before the controller's container starts. | `[]` | | **[Trivy][trivy]** | | | | `trivy.enabled` | The flag to enable Trivy scanner | `true` | | `trivy.image.repository` | Repository for Trivy adapter image | `goharbor/trivy-adapter-photon` | @@ -305,14 +310,15 @@ The following table lists the configurable parameters of the Harbor chart and th | `trivy.ignoreUnfixed` | The flag to display only fixed vulnerabilities | `false` | | `trivy.insecure` | The flag to skip verifying registry certificate | `false` | | `trivy.skipUpdate` | The flag to disable [Trivy DB][trivy-db] downloads from GitHub | `false` | -| `trivy.skipJavaDBUpdate` | If the flag is enabled you have to manually download the `trivy-java.db` file [Trivy Java DB][trivy-java-db] and mount it in the `/home/scanner/.cache/trivy/java-db/trivy-java.db` path | `false` | +| `trivy.skipJavaDBUpdate` | If the flag is enabled you have to manually download the `trivy-java.db` file [Trivy Java DB][trivy-java-db] and mount it in the `/home/scanner/.cache/trivy/java-db/trivy-java.db` path | `false` | | `trivy.offlineScan` | The flag prevents Trivy from sending API requests to identify dependencies. | `false` | | `trivy.securityCheck` | Comma-separated list of what security issues to detect. | `vuln` | | `trivy.timeout` | The duration to wait for scan completion | `5m0s` | | `trivy.gitHubToken` | The GitHub access token to download [Trivy DB][trivy-db] (see [GitHub rate limiting][trivy-rate-limiting]) | | | `trivy.priorityClassName` | The priority class to run the pod as | | | `trivy.topologySpreadConstraints` | The priority class to run the pod as | | -| `trivy.initContainers` | Init containers to be run before the controller's container starts. | `[]` | +| `trivy.initContainers` | Init containers to be run before the controller's container starts. | `[]` | +| `trivy.lifecycle` | Container lifecycle | `{}` | | **Database** | | | | `database.type` | If external database is used, set it to `external` | `internal` | | `database.internal.image.repository` | Repository for database image | `goharbor/harbor-db` | @@ -329,13 +335,13 @@ The following table lists the configurable parameters of the Harbor chart and th | `database.internal.priorityClassName` | The priority class to run the pod as | | | `database.internal.livenessProbe.timeoutSeconds` | The timeout used in liveness probe; 1 to 5 seconds | 1 | | `database.internal.readinessProbe.timeoutSeconds` | The timeout used in readiness probe; 1 to 5 seconds | 1 | -| `database.internal.extrInitContainers` | Extra init containers to be run before the database's container starts. | `[]` | +| `database.internal.extrInitContainers` | Extra init containers to be run before the database's container starts. | `[]` | | `database.external.host` | The hostname of external database | `192.168.0.1` | | `database.external.port` | The port of external database | `5432` | | `database.external.username` | The username of external database | `user` | | `database.external.password` | The password of external database | `password` | | `database.external.coreDatabase` | The database used by core service | `registry` | -| `database.external.existingSecret` | An existing password containing the database password. the key must be `password`. | `""` | +| `database.external.existingSecret` | An existing password containing the database password. the key must be `password`. | `""` | | `database.external.sslmode` | Connection method of external database (require, verify-full, verify-ca, disable) | `disable` | | `database.maxIdleConns` | The maximum number of connections in the idle connection pool. If it <=0, no idle connections are retained. | `50` | | `database.maxOpenConns` | The maximum number of open connections to the database. If it <= 0, then there is no limit on the number of open connections. | `100` | @@ -353,20 +359,21 @@ The following table lists the configurable parameters of the Harbor chart and th | `redis.internal.jobserviceDatabaseIndex` | The database index for jobservice | `1` | | `redis.internal.registryDatabaseIndex` | The database index for registry | `2` | | `redis.internal.trivyAdapterIndex` | The database index for trivy adapter | `5` | -| `redis.internal.harborDatabaseIndex` | The database index for harbor miscellaneous business logic | `0` | -| `redis.internal.cacheLayerDatabaseIndex` | The database index for harbor cache layer | `0` | -| `redis.internal.initContainers` | Init containers to be run before the redis's container starts. | `[]` | +| `redis.internal.harborDatabaseIndex` | The database index for harbor miscellaneous business logic | `0` | +| `redis.internal.cacheLayerDatabaseIndex` | The database index for harbor cache layer | `0` | +| `redis.internal.initContainers` | Init containers to be run before the redis's container starts. | `[]` | +| `redis.internal.lifecycle` | Container lifecycle | `{}` | | `redis.external.addr` | The addr of external Redis: :. When using sentinel, it should be :,:,: | `192.168.0.2:6379` | | `redis.external.sentinelMasterSet` | The name of the set of Redis instances to monitor | | | `redis.external.coreDatabaseIndex` | The database index for core | `0` | | `redis.external.jobserviceDatabaseIndex` | The database index for jobservice | `1` | | `redis.external.registryDatabaseIndex` | The database index for registry | `2` | | `redis.external.trivyAdapterIndex` | The database index for trivy adapter | `5` | -| `redis.external.harborDatabaseIndex` | The database index for harbor miscellaneous business logic | `0` | -| `redis.external.cacheLayerDatabaseIndex` | The database index for harbor cache layer | `0` | +| `redis.external.harborDatabaseIndex` | The database index for harbor miscellaneous business logic | `0` | +| `redis.external.cacheLayerDatabaseIndex` | The database index for harbor cache layer | `0` | | `redis.external.username` | The username of external Redis | | | `redis.external.password` | The password of external Redis | | -| `redis.external.existingSecret` | Use an existing secret to connect to redis. The key must be `REDIS_PASSWORD`. | `""` | +| `redis.external.existingSecret` | Use an existing secret to connect to redis. The key must be `REDIS_PASSWORD`. | `""` | | `redis.podAnnotations` | Annotations to add to the redis pod | `{}` | | **Exporter** | | | | `exporter.replicas` | The replica count | `1` | @@ -382,6 +389,7 @@ The following table lists the configurable parameters of the Harbor chart and th | `exporter.cacheDuration` | the cache duration for information that exporter collected from Harbor | `30` | | `exporter.cacheCleanInterval` | cache clean interval for information that exporter collected from Harbor | `14400` | | `exporter.priorityClassName` | The priority class to run the pod as | | +| `exporter.lifecycle` | Container lifecycle | `{}` | | **Metrics** | | | | `metrics.enabled` | if enable harbor metrics | `false` | | `metrics.core.path` | the url path for core metrics | `/metrics` | @@ -412,8 +420,8 @@ The following table lists the configurable parameters of the Harbor chart and th | `trace.otel.insecure` | Whether establish insecure connection or not for otel | `true` | | `trace.otel.timeout` | The timeout in seconds of otel | `10` | | **Cache** | | | -| `cache.enabled` | Enable cache layer or not | `false` | -| `cache.expireHours` | The expire hours of cache layer | `24` | +| `cache.enabled` | Enable cache layer or not | `false` | +| `cache.expireHours` | The expire hours of cache layer | `24` | [resources]: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/ [trivy]: https://github.com/aquasecurity/trivy diff --git a/templates/core/core-dpl.yaml b/templates/core/core-dpl.yaml index 4705c5f6e..93017304b 100644 --- a/templates/core/core-dpl.yaml +++ b/templates/core/core-dpl.yaml @@ -90,6 +90,10 @@ spec: port: {{ template "harbor.core.containerPort" . }} failureThreshold: 2 periodSeconds: 10 +{{- with .Values.core.lifecycle }} + lifecycle: +{{ toYaml . | indent 10 }} +{{- end }} envFrom: - configMapRef: name: "{{ template "harbor.core" . }}" diff --git a/templates/exporter/exporter-dpl.yaml b/templates/exporter/exporter-dpl.yaml index 32fac20ac..eaa282c08 100644 --- a/templates/exporter/exporter-dpl.yaml +++ b/templates/exporter/exporter-dpl.yaml @@ -73,6 +73,10 @@ spec: port: {{ .Values.metrics.exporter.port }} initialDelaySeconds: 30 periodSeconds: 10 +{{- with .Values.exporter.lifecycle }} + lifecycle: +{{ toYaml . | indent 10 }} +{{- end }} args: ["-log-level", "{{ .Values.logLevel }}"] envFrom: - configMapRef: diff --git a/templates/jobservice/jobservice-dpl.yaml b/templates/jobservice/jobservice-dpl.yaml index 3e426694b..90dd0a9b4 100644 --- a/templates/jobservice/jobservice-dpl.yaml +++ b/templates/jobservice/jobservice-dpl.yaml @@ -86,6 +86,10 @@ spec: port: {{ template "harbor.jobservice.containerPort" . }} initialDelaySeconds: 20 periodSeconds: 10 +{{- with .Values.jobservice.lifecycle }} + lifecycle: +{{ toYaml . | indent 10 }} +{{- end }} {{- if .Values.jobservice.resources }} resources: {{ toYaml .Values.jobservice.resources | indent 10 }} diff --git a/templates/nginx/deployment.yaml b/templates/nginx/deployment.yaml index 04faa3735..69903d589 100644 --- a/templates/nginx/deployment.yaml +++ b/templates/nginx/deployment.yaml @@ -82,6 +82,10 @@ spec: port: {{ .port }} initialDelaySeconds: 1 periodSeconds: 10 +{{- with .Values.nginx.lifecycle }} + lifecycle: +{{ toYaml . | indent 10 }} +{{- end }} {{- if .Values.nginx.resources }} resources: {{ toYaml .Values.nginx.resources | indent 10 }} diff --git a/templates/portal/deployment.yaml b/templates/portal/deployment.yaml index 88bcd4979..5ee96196d 100644 --- a/templates/portal/deployment.yaml +++ b/templates/portal/deployment.yaml @@ -88,6 +88,10 @@ spec: port: {{ template "harbor.portal.containerPort" . }} initialDelaySeconds: 1 periodSeconds: 10 +{{- with .Values.portal.lifecycle }} + lifecycle: +{{ toYaml . | indent 10 }} +{{- end }} ports: - containerPort: {{ template "harbor.portal.containerPort" . }} volumeMounts: diff --git a/templates/redis/statefulset.yaml b/templates/redis/statefulset.yaml index fa5dd22d2..af8673d74 100644 --- a/templates/redis/statefulset.yaml +++ b/templates/redis/statefulset.yaml @@ -63,6 +63,10 @@ spec: port: 6379 initialDelaySeconds: 1 periodSeconds: 10 +{{- with .Values.redis.internal.lifecycle }} + lifecycle: +{{ toYaml . | indent 10 }} +{{- end }} {{- if .Values.redis.internal.resources }} resources: {{ toYaml .Values.redis.internal.resources | indent 10 }} diff --git a/templates/registry/registry-dpl.yaml b/templates/registry/registry-dpl.yaml index 6310b9de0..f9babade8 100644 --- a/templates/registry/registry-dpl.yaml +++ b/templates/registry/registry-dpl.yaml @@ -89,6 +89,10 @@ spec: port: {{ template "harbor.registry.containerPort" . }} initialDelaySeconds: 1 periodSeconds: 10 +{{- with .Values.registry.registry.lifecycle }} + lifecycle: +{{ toYaml . | indent 10 }} +{{- end }} {{- if .Values.registry.registry.resources }} resources: {{ toYaml .Values.registry.registry.resources | indent 10 }} @@ -228,6 +232,10 @@ spec: port: {{ template "harbor.registryctl.containerPort" . }} initialDelaySeconds: 1 periodSeconds: 10 +{{- with .Values.registry.controller.lifecycle }} + lifecycle: +{{ toYaml . | indent 10 }} +{{- end }} {{- if .Values.registry.controller.resources }} resources: {{ toYaml .Values.registry.controller.resources | indent 10 }} diff --git a/templates/trivy/trivy-sts.yaml b/templates/trivy/trivy-sts.yaml index 7e34ee9c7..4b2a643d4 100644 --- a/templates/trivy/trivy-sts.yaml +++ b/templates/trivy/trivy-sts.yaml @@ -169,6 +169,10 @@ spec: periodSeconds: 10 successThreshold: 1 failureThreshold: 3 +{{- with .Values.trivy.lifecycle }} + lifecycle: +{{ toYaml . | indent 10 }} +{{- end }} resources: {{ toYaml .Values.trivy.resources | indent 12 }} {{- if or (or .Values.internalTLS.enabled .Values.caBundleSecretName) (or (not .Values.persistence.enabled) $trivy.existingClaim) }} diff --git a/values.yaml b/values.yaml index c862337d0..4653a65b2 100644 --- a/values.yaml +++ b/values.yaml @@ -497,6 +497,7 @@ nginx: extraEnvVars: [] nodeSelector: {} tolerations: [] + lifecycle: {} affinity: {} # Spread Pods across failure-domains like regions, availability zones or nodes topologySpreadConstraints: [] @@ -528,6 +529,7 @@ portal: extraEnvVars: [] nodeSelector: {} tolerations: [] + lifecycle: {} affinity: {} # Spread Pods across failure-domains like regions, availability zones or nodes topologySpreadConstraints: [] @@ -572,6 +574,7 @@ core: extraEnvVars: [] nodeSelector: {} tolerations: [] + lifecycle: {} affinity: {} # Spread Pods across failure-domains like regions, availability zones or nodes topologySpreadConstraints: [] @@ -655,6 +658,7 @@ jobservice: extraEnvVars: [] nodeSelector: {} tolerations: [] + lifecycle : {} affinity: {} # Spread Pods across failure-domains like regions, availability zones or nodes topologySpreadConstraints: @@ -709,6 +713,7 @@ registry: # requests: # memory: 256Mi # cpu: 100m + lifecycle: {} extraEnvVars: [] controller: image: @@ -718,6 +723,7 @@ registry: # requests: # memory: 256Mi # cpu: 100m + lifecycle: {} extraEnvVars: [] # set the service account to be used, default if left empty serviceAccountName: "" @@ -727,6 +733,7 @@ registry: revisionHistoryLimit: 10 nodeSelector: {} tolerations: [] + lifecycle: {} affinity: {} # Spread Pods across failure-domains like regions, availability zones or nodes topologySpreadConstraints: [] @@ -812,6 +819,7 @@ trivy: nodeSelector: {} tolerations: [] affinity: {} + lifecycle: {} # Spread Pods across failure-domains like regions, availability zones or nodes topologySpreadConstraints: [] # - maxSkew: 1 @@ -979,6 +987,7 @@ redis: extraEnvVars: [] nodeSelector: {} tolerations: [] + lifecycle: {} affinity: {} ## The priority class to run the pod as priorityClassName: @@ -1045,6 +1054,7 @@ exporter: podLabels: {} nodeSelector: {} tolerations: [] + lifecycle: {} affinity: {} # Spread Pods across failure-domains like regions, availability zones or nodes topologySpreadConstraints: []