Skip to main content

Values

This document describes the configurable values for the Node Helm chart.

Configuration Options​

The Node chart supports various configuration options through values. You can customize the deployment by creating a values.yaml file or passing values directly via the --set flag.

Example​

To install with custom values:

helm install <release-name> welance-charts/node -f values.yaml

Or using --set:

helm install <release-name> welance-charts/node --set key=value

Default Values​

The following is the default values.yaml file for the Node Helm chart:

# Default values for helm-chart.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.

replicaCount: 1
    
db:
 hostname: welance-noprod-serverlessv2-tf.cluster-ccr9p5q6kxw9.eu-central-1.rds.amazonaws.com
     
tls: []
        
##TO BE OVERRIDDEN
storage:
  gid: 1000
  uid: 1000
  fid: fs-0e7fcf2d3c61da878a

image:
  repository: registry.gitlab.com/welance/p222-choco/p222-01-choco.com
  pullPolicy: IfNotPresent
  tag: "dev"
  imagePullSecrets: regcred
  commit:
    sha: ""
    url: ""
    branch: ""

configmap:
  enabled: true

# Default value for config file content
envFileContent: ""

basicAuthSecret:
  enabled: true
  data:
    auth: "<your-basic-auth-secret>"

registryAuthSecret:
  name: regcred
  data:
    auth: "<your-registry-auth-secret>"

deployment:
  nodeSelector: {}
  securityContext:
    enabled: true
    runAsUser: 33
    runAsGroup: 33
    fsGroup: 33
  onepassword:
    enabled: false
    path: ''
  annotations: {}
  port:
    name: http
    containerPort: 8080
    protocol: TCP
  volumes: []


  liveness:
    enabled: true
    httpGet:
      path: /server/health
      port: http

  readiness:
    enabled: true
    httpGet:
      path: /server/health
      port: http

  startup:
    enabled: false # to be enabled if the application needs to reach out dependencies at startup
    httpGet:
      path: /server/startup
      port: http

service:
  name: service-web
  type: ClusterIP
  port: 80

ingresses:
  redirect: []
  live:
    enabled: false
    sites: []
  web:
    name: ingress-web
    enabled: true
    ingressClassName: "welance-develop"
    annotations: {}

s3:
  enabled: false
  accessKeyID: ""
  secretAccessKey: ""
  endpoint: ""

nfs:
  enabled: false
  storageclassName: ""
  
resources: {}
#  limits:
#    cpu: 50m
#    memory: 400Mi
#  requests:
#    cpu: 25m
#    memory: 265Mi


redis:
  enabled: false
  image: 
    repository: "redis"
    tag: "5-alpine"
  resources: 
    limits:
      cpu: 25m
      memory: 265Mi
    requests:
      cpu: 25m
      memory: 265Mi

quota:
  enabled: false
  hard:
    requests.cpu: "1"
    requests.memory: 2Gi
    limits.cpu: "2"
    limits.memory: 4Gi    
    
autoscaling:
  enabled: false
  minReplicas: 1
  maxReplicas: 100
  targetCPUUtilizationPercentage: 80
  targetMemoryUtilizationPercentage: 80

Key Configuration Sections​

Database Configuration (db)​

  • Database connection hostname (minimal configuration)

Image Configuration (image)​

  • Container image repository, tag, pull policy, and image pull secrets
  • Git commit information (SHA, URL, branch)

Deployment Configuration (deployment)​

  • Security context settings
  • Container port configuration (8080)
  • Volume mounts (configurable, empty by default)
  • Health check probes (liveness and readiness enabled by default, startup optional)
  • OnePassword integration support

Service & Ingress (service, ingresses)​

  • Service type and port configuration (port 80)
  • Ingress settings

S3 Configuration (s3)​

  • Optional S3 storage integration
  • Access key ID, secret access key, and endpoint configuration

Resources & Scaling​

  • Resource limits and requests
  • Redis configuration (optional, disabled by default)
  • Resource quotas
  • Horizontal Pod Autoscaling (HPA) settings

Storage​

  • NFS storage configuration (optional)