Skip to main content

Values

This document describes the configurable values for the Welance Operator Helm chart.

Configuration Options​

The Welance Operator 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/welance-operator -f values.yaml

Or using --set:

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

Default Values​

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

replicaCount: 1

installCRDs: false

nodeSelector:
  welance/environment: management  

args:
  - "--zap-log-level=debug"
  - "--zap-devel=true"
  - "--leader-elect=false"
  - "--metrics-bind-address=127.0.0.1:8080"
  - "--health-probe-bind-address=127.0.0.1:8081"
  - "--mysql-db-host=welance-noprod-serverlessv2-tf.cluster-ccr9p5q6kxw9.eu-central-1.rds.amazonaws.com"
  - "--mysql-db-port=3306"
  - "--mysql-db-user=root"
  - "--mysql-db-password=<your-mysql-password>"
  - "--mysql-db-name=welance"
  - "--minio-host=minio-api.noprod.welance.com"
  - "--minio-access-key=<your-minio-access-key>"
  - "--minio-secret-key=<your-minio-secret-key>"

image:
  repository: registry.gitlab.com/welance/platform/applications/s3-welance-operator
  tag: 0.0.4.rc42
  pullPolicy: IfNotPresent
  createPullSecret: true
  pullSecret: minio-operator-regcred
  dockerconfigjson: |
    <your-docker-config-json>

resources:
  limits:
    cpu: 500m
    memory: 128Mi
  requests:
    cpu: 100m
    memory: 64Mi

probes:
  liveness: 
    path: /healthz
    port: 8081
    initialDelaySeconds: 15
    periodSeconds: 20
    timeoutSeconds: 3    
  readiness:
    path: /readyz
    port: 8081
    initialDelaySeconds: 5
    periodSeconds: 10
    timeoutSeconds: 3

Key Configuration Sections​

Replica Count (replicaCount)​

  • Number of operator replicas to deploy (default: 1)

CRD Installation (installCRDs)​

  • Whether to install Custom Resource Definitions (default: false)
  • Set to true if CRDs should be managed by Helm

Node Selector (nodeSelector)​

  • Kubernetes node selector for pod placement
  • Default: welance/environment: management - ensures operator runs on management nodes

Operator Arguments (args)​

  • Command-line arguments passed to the operator
  • Logging: --zap-log-level=debug, --zap-devel=true - debug logging configuration
  • Leader Election: --leader-elect=false - disable leader election (for single replica)
  • Metrics: --metrics-bind-address=127.0.0.1:8080 - metrics endpoint
  • Health Probes: --health-probe-bind-address=127.0.0.1:8081 - health check endpoint
  • MySQL Database: Connection settings (host, port, user, password, database name)
  • MinIO: S3-compatible storage configuration (host, access key, secret key)

Image Configuration (image)​

  • Container image repository and tag
  • Image pull policy
  • Registry authentication configuration
  • Docker config JSON for registry credentials

Resources (resources)​

  • CPU and memory limits and requests
  • Default limits: 500m CPU, 128Mi memory
  • Default requests: 100m CPU, 64Mi memory

Health Probes (probes)​

  • Liveness Probe: /healthz endpoint on port 8081
    • Initial delay: 15 seconds
    • Period: 20 seconds
    • Timeout: 3 seconds
  • Readiness Probe: /readyz endpoint on port 8081
    • Initial delay: 5 seconds
    • Period: 10 seconds
    • Timeout: 3 seconds

Usage​

The Welance Operator is a Kubernetes operator that manages Welance platform resources. It connects to:

  • MySQL database for state management
  • MinIO for S3-compatible object storage

The operator should be deployed on management nodes and typically runs as a single replica with leader election disabled.