2021-05-15 17:02:51 +00:00
|
|
|
replicaCount: 2
|
|
|
|
|
|
|
|
|
|
image:
|
|
|
|
|
registry: docker.io
|
2021-06-18 18:48:22 +00:00
|
|
|
repository: woodpeckerci/woodpecker-agent
|
2021-05-15 17:02:51 +00:00
|
|
|
pullPolicy: Always
|
|
|
|
|
# Overrides the image tag whose default is the chart appVersion.
|
|
|
|
|
tag: ""
|
|
|
|
|
|
|
|
|
|
env:
|
2021-09-24 12:04:54 +00:00
|
|
|
WOODPECKER_SERVER: "woodpecker-server.<namespace>.svc.cluster.local:9000"
|
2021-05-15 17:02:51 +00:00
|
|
|
|
|
|
|
|
extraSecretNamesForEnvFrom:
|
2021-09-24 12:04:54 +00:00
|
|
|
- woodpecker-secret
|
2021-05-15 17:02:51 +00:00
|
|
|
|
|
|
|
|
imagePullSecrets: []
|
|
|
|
|
nameOverride: ""
|
|
|
|
|
fullnameOverride: ""
|
|
|
|
|
|
|
|
|
|
serviceAccount:
|
|
|
|
|
# Specifies whether a service account should be created
|
|
|
|
|
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:'.
|
|
|
|
|
# limits:
|
|
|
|
|
# cpu: 100m
|
|
|
|
|
# memory: 128Mi
|
|
|
|
|
# requests:
|
|
|
|
|
# cpu: 100m
|
|
|
|
|
# memory: 128Mi
|
|
|
|
|
|
|
|
|
|
nodeSelector: {}
|
|
|
|
|
|
|
|
|
|
tolerations: []
|
|
|
|
|
|
|
|
|
|
affinity: {}
|
2021-08-11 15:36:39 +00:00
|
|
|
|
|
|
|
|
## Using topology spread constraints, you can ensure that there is at least one agent
|
|
|
|
|
## pod for each topology zone, e.g. one per arch for for multi-architecture clusters
|
|
|
|
|
## or one for each region for geographically distributed cloud-hosted clusters.
|
|
|
|
|
## Ref: https://kubernetes.io/docs/concepts/workloads/pods/pod-topology-spread-constraints/
|
|
|
|
|
topologySpreadConstraints: []
|
|
|
|
|
# - maxSkew: 1
|
|
|
|
|
# topologyKey: "beta.kubernetes.io/arch"
|
|
|
|
|
# whenUnsatisfiable: "DoNotSchedule"
|
|
|
|
|
# labelSelector:
|
|
|
|
|
# matchLabels:
|
|
|
|
|
# "app.kubernetes.io/name": woodpecker-agent
|
