Skip to main content

Values

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

Configuration Options​

The S3 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/s3 -f values.yaml

Or using --set:

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

Default Values​

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

nameOverride: ""
fullnameOverride: ""

tlsSecret:
  enabled: true
  name: tls-web-secret
  crt: "<your-tls-certificate-base64>"
  key: "<your-tls-private-key-base64>"

tls: []

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

service:
  name: web

bucket:
  url: p007-20-welance-develop.s3-website.eu-central-1.amazonaws.com

ingresses:
  redirect: []
  live:
    enabled: false
    sites: []
  web:
    name: ingress-web
    enabled: true
    ingressClassName: "welance-develop"
    annotations:
      nginx.ingress.kubernetes.io/auth-type: basic
      nginx.ingress.kubernetes.io/auth-secret: ingress-secret # name of the secret that contains the user/password definitions
      nginx.ingress.kubernetes.io/backend-protocol: http
      nginx.ingress.kubernetes.io/from-to-www-redirect: 'true'
      nginx.ingress.kubernetes.io/upstream-vhost: p007-20-develop.s3-website.eu-central-1.amazonaws.com
    hosts:
      - paths:
          - backend:
              service:
                name: web
                port:
                  number: 80
            path: /
            pathType: Prefix    
    tls:
      - secretName: tls-web-secret
  
quota:
  enabled: false
  hard:
    requests.cpu: "0"
    requests.memory: 0Gi
    limits.cpu: "0"
    limits.memory: 0Gi

Key Configuration Sections​

Name Override (nameOverride, fullnameOverride)​

  • Override default naming conventions for resources

TLS Secret (tlsSecret)​

  • TLS certificate and private key configuration
  • Enable/disable TLS secret creation
  • Certificate and key in base64 format

Basic Authentication (basicAuthSecret)​

  • Basic authentication configuration for ingress
  • User/password definitions

Service Configuration (service)​

  • Service name configuration
  • Used for ingress backend routing

Bucket Configuration (bucket)​

  • S3 bucket URL configuration
  • Points to the S3 website endpoint

Ingress Configuration (ingresses)​

  • Ingress settings for exposing S3 website
  • Basic authentication
  • Backend protocol (HTTP)
  • WWW redirect configuration
  • Upstream virtual host (S3 website endpoint)
  • TLS configuration with secret name
  • Path-based routing

Resource Quotas (quota)​

  • Resource quota settings (disabled by default)
  • CPU and memory limits

Usage​

This chart is designed to create an ingress that proxies requests to an S3 static website. The ingress acts as a reverse proxy, forwarding requests to the S3 website endpoint while providing:

  • TLS/SSL termination
  • Basic authentication
  • WWW redirect functionality
  • Custom domain support