Skip to content

chaser100/u-helm-chart

BranchesTags

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

40 Commits
docs
docs
 
 
helm-charts/application
helm-charts/application
 
 
.gitignore
.gitignore
 
 
CHANGELOG.md
CHANGELOG.md
 
 
LICENSE
LICENSE
 
 
README.md
README.md
 
 

Repository files navigation

Universal Helm Chart

A comprehensive and flexible Helm chart for deploying applications to Kubernetes. This chart provides a universal template that supports a wide range of deployment scenarios including deployments, services, ingress, Gateway API routes, jobs, cronjobs, and advanced features like autoscaling, sidecar containers, and custom manifests.

Chart Version: 0.2.6

Features

  • Flexible Deployment Configuration - Deploy applications with customizable replica counts, resource limits, and security contexts
  • Ingress and Gateway API Routing - Support for standard ingress, extra ingress, plain ingress with automatic service creation, and Gateway API HTTPRoute
  • Job and CronJob Support - Run one-time jobs and scheduled cronjobs with full configuration options
  • Autoscaling - Horizontal Pod Autoscaler (HPA) support with CPU and memory metrics
  • Security - Configurable security contexts, service accounts, and pod security policies
  • Volume Management - Support for ConfigMaps, Secrets, and PersistentVolumeClaims
  • Sidecar Containers - Deploy additional containers alongside your main application
  • Custom Manifests - Inject raw Kubernetes manifests for advanced use cases
  • Environment Variables - Flexible configuration for environment variables (plain values, secrets, and envFrom)

Installation

This chart is published via GitHub Pages and can be used as an external Helm repository.

Add the Helm Repository

helm repo add uni-chart https://chaser100.github.io/u-helm-chart
helm repo update

Install the Chart

# Basic installation
helm install my-release uni-chart/application

# Installation with custom values
helm install my-release uni-chart/application -f my-values.yaml

# Installation with specific version
helm install my-release uni-chart/application --version 0.2.6

Upgrade the Chart

helm upgrade my-release uni-chart/application -f my-values.yaml

Uninstall the Chart

helm uninstall my-release

Configuration

The following table lists the configurable parameters and their default values. You can override these values by creating a custom values.yaml file or using the --set flag during installation.

Deployment Configuration

Parameter Description Default
replicaCount Number of replicas for the deployment 1
image Container image name nginx
imageTag Container image tag latest
imagePullPolicy Image pull policy Always
imagePullSecrets List of image pull secrets for private registries []
nameOverride Override the name of the chart ""
fullnameOverride Override the full name of the chart ""
deploymentAnnotations Additional annotations for the deployment []
podAnnotations Additional annotations for pods {}
podLabels Additional labels for pods {}

Example

replicaCount: 3
image: myregistry/myapp
imageTag: v1.2.3
imagePullPolicy: IfNotPresent
imagePullSecrets:
  - name: regcred

Service Account

Parameter Description Default
serviceAccount.create Whether to create a service account true
serviceAccount.automount Automatically mount the service account token true
serviceAccount.annotations Additional annotations for the service account {}
serviceAccount.name Name of the service account (if not set, uses fullname) ""

Example

serviceAccount:
  create: true
  automount: true
  annotations:
    eks.amazonaws.com/role-arn: arn:aws:iam::123456789012:role/my-role
  name: my-service-account

Security Context

Parameter Description Default
podSecurityContext Security context for the pod {}
shareProcessNamespace Enable process namespace sharing between containers in the pod false
securityContext Security context for the container {}

Note: When shareProcessNamespace is set to true, containers in the pod can see and signal processes from other containers in the same pod. This is useful for debugging and monitoring scenarios, but should be used with caution as it reduces process isolation.

Example

podSecurityContext:
  fsGroup: 2000
  runAsNonRoot: true
  runAsUser: 1000

shareProcessNamespace: true

securityContext:
  capabilities:
    drop:
    - ALL
  readOnlyRootFilesystem: true
  allowPrivilegeEscalation: false

Service

Parameter Description Default
service.name Name of the service port http
service.type Type of service (ClusterIP, NodePort, LoadBalancer) ClusterIP
service.port Service port 80
service.protocol Service protocol TCP

Example

service:
  name: http
  type: LoadBalancer
  port: 8080
  protocol: TCP

Ingress

Parameter Description Default
ingress.enabled Enable ingress false
ingress.className Ingress controller class name ""
ingress.annotations Ingress annotations {}
ingress.hosts List of ingress hosts and paths See values.yaml
ingress.tls TLS configuration for ingress []

Example

ingress:
  enabled: true
  className: nginx
  annotations:
    cert-manager.io/cluster-issuer: letsencrypt-prod
    nginx.ingress.kubernetes.io/rewrite-target: /
  hosts:
    - host: example.com
      paths:
        - path: /
          pathType: Prefix
    - host: api.example.com
      paths:
        - path: /api
          pathType: Prefix
  tls:
    - secretName: example-tls
      hosts:
        - example.com
        - api.example.com

Extra Ingress

An additional ingress resource with the same structure as the main ingress.

Parameter Description Default
extra.ingress.enabled Enable extra ingress false
extra.ingress.className Ingress controller class name ""
extra.ingress.annotations Ingress annotations {}
extra.ingress.hosts List of ingress hosts and paths See values.yaml
extra.ingress.tls TLS configuration for ingress []

Gateway API Route

Creates a gateway.networking.k8s.io/v1 HTTPRoute resource and automatically routes traffic to the Service created by this chart ({{ include "application.fullname" . }} on service.port).

Parameter Description Default
route.enabled Enable HTTPRoute creation false
route.name HTTPRoute name (uses chart fullname if empty) ""
route.labels Additional HTTPRoute labels {}
route.annotations HTTPRoute annotations {}
route.gateway Gateway name for parentRefs ""
route.gatewayNamespace Gateway namespace for parentRefs (optional) ""
route.sectionName Gateway listener/section name (optional) ""
route.hostname Route hostname chart-example.local
route.path Path match value /
route.pathMatchType Path match type PathPrefix
route.backendWeight Backend reference weight 1

route.gateway is required when route.enabled: true. route template is rendered only when deployment (and chart service) is enabled (deploymentDisable: false).

Example

route:
  enabled: true
  gateway: internal
  gatewayNamespace: kgateway-system
  sectionName: https-internal-wildcard
  hostname: app.internal.example.com
  path: /
  pathMatchType: PathPrefix
  backendWeight: 1

Plain Ingress

A flexible feature for creating arbitrary Ingress resources with advanced configuration, including automatic service creation.

Parameter Description Default
ingressPlain.enabled Enable plain ingress false
ingressPlain.items List of ingress objects []

Each item in ingressPlain.items supports:

  • name - Ingress name (auto-generated if not specified)
  • className - Ingress controller class
  • annotations - Ingress annotations
  • labels - Additional labels
  • tls - TLS configuration:
    • secretName - TLS secret name
    • hosts - List of hosts
  • rules - List of ingress rules:
    • host - Domain name
    • paths - List of paths:
      • path - Route path (e.g., /api)
      • pathType - Path type (Prefix, Exact, ImplementationSpecific)
      • backend.service.name - Backend service name
      • backend.service.port - Backend service port
      • createService - Whether to automatically create a Service for this path
      • service - Service configuration (optional):
        • type - Service type (ClusterIP, NodePort, LoadBalancer)
        • port, targetPort, portName, protocol - Service port configuration
        • selector - Pod selector labels
        • annotations, labels - Service metadata

Example

ingressPlain:
  enabled: true
  items:
    - name: public-api
      className: nginx
      annotations:
        nginx.ingress.kubernetes.io/rewrite-target: /
        cert-manager.io/cluster-issuer: letsencrypt-prod
      rules:
        - host: api.example.com
          paths:
            - path: /
              backend:
                service:
                  name: users-service
                  port: 8080
              createService: true
              service:
                type: ClusterIP
                selector:
                  app: users
                port: 8080
                targetPort: 8080
            - path: /orders
              backend:
                service:
                  name: orders-service
                  port: 9090
              createService: false
      tls:
        - secretName: api-tls
          hosts:
            - api.example.com

Health Probes

Parameter Description Default
livenessProbe Liveness probe configuration {}
readinessProbe Readiness probe configuration {}
startupProbe Startup probe configuration {}

Example

livenessProbe:
  httpGet:
    path: /health
    port: http
  initialDelaySeconds: 30
  periodSeconds: 10
  timeoutSeconds: 5
  failureThreshold: 3

readinessProbe:
  httpGet:
    path: /ready
    port: http
  initialDelaySeconds: 5
  periodSeconds: 5
  timeoutSeconds: 3
  failureThreshold: 3

startupProbe:
  httpGet:
    path: /startup
    port: http
  initialDelaySeconds: 10
  periodSeconds: 10
  timeoutSeconds: 5
  failureThreshold: 30

Autoscaling

Parameter Description Default
autoscaling.enabled Enable Horizontal Pod Autoscaler false
autoscaling.minReplicas Minimum number of replicas 1
autoscaling.maxReplicas Maximum number of replicas 100
autoscaling.targetCPUUtilizationPercentage Target CPU utilization percentage 80
autoscaling.targetMemoryUtilizationPercentage Target memory utilization percentage (optional) null

Example

autoscaling:
  enabled: true
  minReplicas: 2
  maxReplicas: 10
  targetCPUUtilizationPercentage: 70
  targetMemoryUtilizationPercentage: 80

Resources

Parameter Description Default
resources.requests Resource requests (CPU, memory) {}
resources.limits Resource limits (CPU, memory) {}

Example

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

ConfigMaps

Mount ConfigMaps as volumes in the pod.

Parameter Description Default
configMaps List of ConfigMap configurations {}

Each ConfigMap entry supports:

  • name - ConfigMap name
  • mountPath - Mount path in the container
  • readOnly - Whether the volume is read-only
  • defaultMode - Default file mode (e.g., 0440)
  • subPath - Subpath within the volume (optional)
  • items - List of items to include (optional)
  • data - ConfigMap data

Example

configMaps:
  - name: app-config
    mountPath: /etc/app-config
    readOnly: true
    defaultMode: 0440
    data:
      app.conf: |
        debug = true
        log_level = info
  - name: partial-config
    mountPath: /etc/partial
    subPath: app.conf
    readOnly: false
    items:
      - key: app.conf
        path: config-file
    data:
      app.conf: |
        key=value

PersistentVolumeClaims

Create and manage PersistentVolumeClaims (PVCs) for persistent storage. PVCs are automatically mounted in the main container, init containers, and sidecar containers when mountPath is specified.

Parameter Description Default
persistentVolumeClaims List of PVC definitions []

Each PVC entry supports:

  • name - PVC name (required)
  • size - Storage size (e.g., "10Gi", defaults to "1Gi" if not specified)
  • storageClassName - Storage class name (optional)
  • accessModes - List of access modes (defaults to ["ReadWriteOnce"] if not specified)
  • mountPath - Mount path in containers (optional, if specified, PVC will be automatically mounted)
  • readOnly - Whether the volume is read-only (defaults to false)
  • subPath - Subpath within the volume (optional)
  • annotations - Additional annotations for the PVC
  • resources - Custom resources specification (overrides size if specified)
  • volumeMode - Volume mode (Filesystem or Block)
  • dataSource - Data source for cloning volumes
  • selector - Label selector for volume binding

Note: When mountPath is specified, the PVC is automatically:

  • Added to the pod's volumes
  • Mounted in the main container only

PVCs from persistentVolumeClaims are not automatically mounted in init containers or sidecar containers. To use persistent storage in init containers or sidecar containers, configure individual pvc settings for each container.

Example

persistentVolumeClaims:
  - name: data-storage
    size: 10Gi
    storageClassName: fast-ssd
    accessModes:
      - ReadWriteOnce
    mountPath: /data
    readOnly: false
  - name: logs-storage
    size: 5Gi
    storageClassName: standard
    accessModes:
      - ReadWriteOnce
    mountPath: /var/log
    readOnly: false
  - name: shared-storage
    size: 20Gi
    storageClassName: nfs
    accessModes:
      - ReadWriteMany
    mountPath: /shared
    annotations:
      volume.beta.kubernetes.io/storage-class: nfs

Using PVCs in Init Containers

Each init container can have its own PVC configured individually:

initContainers:
  enabled: true
  containers:
    - name: init-migration
      image: myapp
      command: ["/bin/sh", "-c"]
      args: ["python manage.py migrate"]
      pvc:
        enabled: true
        name: init-migration-pvc
        size: 5Gi
        storageClassName: standard
        accessModes:
          - ReadWriteOnce
        mountPath: /data
        readOnly: false

Using PVCs in Sidecar Containers

Each sidecar container can have its own PVC configured individually:

extraContainers:
  enabled: true
  containers:
    - name: log-collector
      image: fluent/fluent-bit:latest
      pvc:
        enabled: true
        name: log-collector-pvc
        size: 10Gi
        storageClassName: standard
        accessModes:
          - ReadWriteOnce
        mountPath: /var/log
        readOnly: false

Volumes

Additional volumes for mounting ConfigMaps, Secrets, and other volume types.

Parameter Description Default
volumes List of volume definitions {}
volumeMounts List of volume mount definitions {}

Example

volumes:
  - name: custom-secret
    secret:
      secretName: mysecret
      optional: false
  - name: temp-storage
    emptyDir: {}

volumeMounts:
  - name: custom-secret
    mountPath: "/etc/secrets"
    readOnly: true
  - name: temp-storage
    mountPath: "/tmp"

Pod Scheduling

Parameter Description Default
nodeSelector Node selector labels []
tolerations Pod tolerations {}
affinity Pod affinity/anti-affinity rules {}

Example

nodeSelector:
  node-role.kubernetes.io/app: ""

tolerations:
  - key: "node-role.kubernetes.io/app"
    operator: "Exists"
    effect: "NoSchedule"

affinity:
  podAntiAffinity:
    preferredDuringSchedulingIgnoredDuringExecution:
      - weight: 100
        podAffinityTerm:
          labelSelector:
            matchExpressions:
              - key: app.kubernetes.io/name
                operator: In
                values:
                  - application
          topologyKey: kubernetes.io/hostname

Init Containers

Run initialization containers that complete before the main application containers start. Useful for database migrations, file downloads, or other setup tasks.

Parameter Description Default
initContainers.enabled Enable init containers false
initContainers.containers List of init container definitions []

Each init container supports:

  • name - Container name (required)
  • image - Container image (required)
  • imageTag - Container image tag (defaults to main imageTag if not set)
  • imagePullPolicy - Image pull policy (defaults to main imagePullPolicy if not set)
  • command - Container command
  • args - Container arguments
  • env - Plain environment variables
  • envFromSecrets - Environment variables from secrets
  • envFrom - Environment variables from ConfigMaps or Secrets
  • volumeMounts - Volume mounts
  • pvc - Individual PVC configuration for this init container (optional)
    • enabled - Enable PVC creation (default: false)
    • name - PVC name (defaults to {container-name}-pvc if not set)
    • size - Storage size (e.g., "5Gi", defaults to "1Gi")
    • storageClassName - Storage class name
    • accessModes - List of access modes (defaults to ["ReadWriteOnce"])
    • mountPath - Mount path in the container
    • readOnly - Whether the volume is read-only (default: false)
    • subPath - Subpath within the volume (optional)
    • annotations - Additional annotations for the PVC
    • resources - Custom resources specification
    • volumeMode - Volume mode (Filesystem or Block)
    • dataSource - Data source for cloning volumes
    • selector - Label selector for volume binding
  • resources - Resource requests and limits
  • securityContext - Security context for the init container

Note: Init containers inherit global env variables from the root level. They run sequentially and must complete successfully before the main containers start. PVCs defined in persistentVolumeClaims are not automatically mounted in init containers - use individual pvc configuration if you need persistent storage for init containers.

Example

initContainers:
  enabled: true
  containers:
    - name: init-migration
      image: myapp
      imageTag: v1.0.0
      imagePullPolicy: IfNotPresent
      command: ["/bin/sh", "-c"]
      args: ["python manage.py migrate"]
      env:
        - name: INIT_ENV
          value: production
      envFromSecrets:
        - name: DB_PASSWORD
          secretName: db-secret
          secretKey: password
      envFrom:
        - secretRef:
            name: app-secrets
        - configMapRef:
            name: app-config
      volumeMounts:
        - name: init-data
          mountPath: /mnt/init
      securityContext:
        runAsNonRoot: true
        runAsUser: 1000
      resources:
        requests:
          cpu: 50m
          memory: 64Mi
        limits:
          cpu: 100m
          memory: 128Mi
    - name: init-download
      image: busybox:latest
      command: ["/bin/sh", "-c"]
      args: ["wget -O /data/config.json https://example.com/config.json"]
      volumeMounts:
        - name: shared-data
          mountPath: /data

Sidecar Containers

Deploy additional containers alongside the main application container.

Parameter Description Default
extraContainers.enabled Enable sidecar containers false
extraContainers.containers List of sidecar container definitions []

Each sidecar container supports the same parameters as init containers, including individual pvc configuration.

Example

extraContainers:
  enabled: true
  containers:
    - name: sidecar
      image: busybox:latest
      command: ["sleep", "3600"]
      env:
        - name: SIDECAR_ENV
          value: production
      envFromSecrets:
        - name: BAR
          secretName: example-external-secret
          secretKey: BAR
      volumeMounts:
        - name: my-config
          mountPath: /mnt/config
      pvc:
        enabled: true
        name: sidecar-pvc
        size: 10Gi
        storageClassName: standard
        accessModes:
          - ReadWriteOnce
        mountPath: /var/log
        readOnly: false
      resources:
        requests:
          cpu: 50m
          memory: 64Mi
        limits:
          cpu: 100m
          memory: 128Mi

Note: Each sidecar container can have its own env variables. Global env variables from the root level are also inherited by all sidecar containers. PVCs defined in persistentVolumeClaims are not automatically mounted in sidecar containers - use individual pvc configuration if you need persistent storage for sidecar containers.

Environment Variables

The chart supports three ways to configure environment variables:

  1. Plain environment variables - Simple key-value pairs
  2. Environment variables from secrets - Load specific keys from Kubernetes secrets
  3. Environment variables from secrets (envFrom) - Load all keys from a secret

Plain Environment Variables

Parameter Description Default
env List of plain environment variables []

This is useful for non-sensitive configuration values or when using tools like Bank Vaults webhooks that will mutate the deployment and add secret values later.

Example

env:
  - name: ENVIRONMENT
    value: production
  - name: LOG_LEVEL
    value: info
  - name: APP_NAME
    value: my-app
  - name: API_HOST
    value: api.example.com

Environment Variables from Secrets

Parameter Description Default
envFromSecrets.enableEnvFrom Enable loading all keys from a secret as env vars false
envFromSecrets.secretName Secret name for envFrom ""
envSecrets.enableEnv Enable loading specific keys from secrets false
envSecrets.envs List of environment variable definitions from secrets []

Example with Bank Vaults Webhooks

When using Bank Vaults webhooks, you can define plain environment variables in values.yaml and add annotations. Bank Vaults will mutate the deployment after creation and inject secret values:

podAnnotations:
  vault.security.banzaicloud.io/vault-addr: "https://vault.example.com:8200"
  vault.security.banzaicloud.io/vault-role: "my-app-role"
  vault.security.banzaicloud.io/vault-path: "kubernetes"
  vault.security.banzaicloud.io/vault-skip-verify: "false"

env:
  - name: DATABASE_URL
    value: ""  # Will be injected by Bank Vaults
  - name: API_KEY
    value: ""  # Will be injected by Bank Vaults
  - name: ENVIRONMENT
    value: production  # Plain value, not from vault

Example with Secrets

env:
  - name: ENVIRONMENT
    value: production

envFromSecrets:
  enableEnvFrom: true
  secretName: example-external-secret

envSecrets:
  enableEnv: true
  envs:
    - name: API_KEY
      secretName: my-secret
      secretKey: API_KEY
    - name: DATABASE_URL
      secretName: db-secret
      secretKey: connection-string

Job

Run a one-time Kubernetes Job.

Parameter Description Default
job.enabled Enable the job false
job.name Job name my-job
job.image Container image busybox
job.imageTag Container image tag latest
job.imagePullPolicy Image pull policy IfNotPresent
job.restartPolicy Restart policy OnFailure
job.backoffLimit Number of retries before marking as failed 2
job.command Container command ["/bin/sh", "-c"]
job.args Container arguments []
job.env Plain environment variables []
job.envFromSecrets Environment variables from secrets []
job.resources Resource requests and limits {}

Example

job:
  enabled: true
  name: migration-job
  image: postgres:14
  imageTag: latest
  imagePullPolicy: IfNotPresent
  restartPolicy: OnFailure
  backoffLimit: 3
  command: ["/bin/bash", "-c"]
  args: ["psql -h $DB_HOST -U $DB_USER -d $DB_NAME -f /migrations/init.sql"]
  env:
    - name: MIGRATION_ENV
      value: production
  envFromSecrets:
    - name: DB_HOST
      secretName: db-secret
      secretKey: host
    - name: DB_USER
      secretName: db-secret
      secretKey: user
    - name: DB_NAME
      secretName: db-secret
      secretKey: database
  resources:
    requests:
      cpu: 100m
      memory: 128Mi
    limits:
      cpu: 500m
      memory: 256Mi

CronJob

Run scheduled Kubernetes CronJobs.

Parameter Description Default
cronjob.enabled Enable the cronjob false
cronjob.name CronJob name my-cronjob
cronjob.image Container image busybox
cronjob.imageTag Container image tag latest
cronjob.imagePullPolicy Image pull policy IfNotPresent
cronjob.schedule Cron schedule expression "*/5 * * * *"
cronjob.restartPolicy Restart policy OnFailure
cronjob.backoffLimit Number of retries 1
cronjob.successfulJobsHistoryLimit Number of successful jobs to keep 2
cronjob.failedJobsHistoryLimit Number of failed jobs to keep 1
cronjob.command Container command ["/bin/sh", "-c"]
cronjob.args Container arguments []
cronjob.env Plain environment variables []
cronjob.envFromSecrets Environment variables from secrets []
cronjob.resources Resource requests and limits {}

Example

cronjob:
  enabled: true
  name: backup-cronjob
  image: postgres:14
  imageTag: latest
  imagePullPolicy: IfNotPresent
  schedule: "0 2 * * *"  # Daily at 2 AM
  restartPolicy: OnFailure
  backoffLimit: 2
  successfulJobsHistoryLimit: 3
  failedJobsHistoryLimit: 2
  command: ["/bin/bash", "-c"]
  args: ["pg_dump -h $DB_HOST -U $DB_USER -d $DB_NAME > /backups/backup-$(date +%Y%m%d).sql"]
  env:
    - name: BACKUP_ENV
      value: production
  envFromSecrets:
    - name: DB_HOST
      secretName: db-secret
      secretKey: host
    - name: DB_USER
      secretName: db-secret
      secretKey: user
    - name: DB_NAME
      secretName: db-secret
      secretKey: database
  resources:
    requests:
      cpu: 200m
      memory: 256Mi
    limits:
      cpu: 500m
      memory: 512Mi

Extra Manifests

Inject raw Kubernetes manifests for advanced use cases (e.g., ExternalSecrets, custom CRDs).

Parameter Description Default
extraManifests List of Kubernetes manifest objects {}

Important: Resources of kind ExternalSecret are automatically configured with Helm pre-install/pre-upgrade hooks to ensure they are created before the deployment. This prevents ConfigContainerError when the deployment tries to use secrets that haven't been created yet.

Example

extraManifests:
  - apiVersion: external-secrets.io/v1beta1
    kind: ExternalSecret
    metadata:
      name: example-external-secret
      namespace: default
    spec:
      refreshInterval: 10s
      secretStoreRef:
        name: vault-cluster-backend
        kind: ClusterSecretStore
      target:
        name: example-external-secret
        template:
          type: Opaque
      data:
        - secretKey: FOO
          remoteRef:
            key: path/keys
            property: FOO
        - secretKey: BAR
          remoteRef:
            key: path/keys
            property: BAR

Note: For ExternalSecret resources, the chart automatically adds the following Helm hook annotations:

  • helm.sh/hook: pre-install,pre-upgrade - Ensures creation before deployment
  • helm.sh/hook-weight: "-5" - Sets execution order (negative weight means earlier execution)
  • helm.sh/hook-delete-policy: before-hook-creation - Cleans up old resources before creating new ones

Usage Examples

Basic Web Application

replicaCount: 2
image: nginx
imageTag: 1.21
service:
  type: ClusterIP
  port: 80
ingress:
  enabled: true
  className: nginx
  hosts:
    - host: app.example.com
      paths:
        - path: /
          pathType: Prefix
resources:
  requests:
    cpu: 100m
    memory: 128Mi
  limits:
    cpu: 200m
    memory: 256Mi

Application with Database Migration Job

replicaCount: 3
image: myapp
imageTag: v1.0.0
job:
  enabled: true
  name: db-migration
  image: myapp
  imageTag: v1.0.0
  command: ["/bin/sh", "-c"]
  args: ["npm run migrate"]
  envFromSecrets:
    - name: DATABASE_URL
      secretName: db-secret
      secretKey: url

Application with Autoscaling

replicaCount: 2
image: myapp
imageTag: v1.0.0
autoscaling:
  enabled: true
  minReplicas: 2
  maxReplicas: 10
  targetCPUUtilizationPercentage: 70
resources:
  requests:
    cpu: 200m
    memory: 256Mi
  limits:
    cpu: 1000m
    memory: 512Mi

Application with Init Container and Individual PVC

replicaCount: 2
image: myapp
imageTag: v1.0.0
persistentVolumeClaims:
  - name: data-storage
    size: 10Gi
    mountPath: /data

initContainers:
  enabled: true
  containers:
    - name: init-migration
      image: myapp
      imageTag: v1.0.0
      command: ["/bin/sh", "-c"]
      args: ["python manage.py migrate"]
      envFromSecrets:
        - name: DATABASE_URL
          secretName: db-secret
          secretKey: url
      pvc:
        enabled: true
        name: init-migration-pvc
        size: 5Gi
        storageClassName: standard
        accessModes:
          - ReadWriteOnce
        mountPath: /mnt/init

Application with PersistentVolumeClaim

replicaCount: 2
image: myapp
imageTag: v1.0.0
persistentVolumeClaims:
  - name: data-storage
    size: 10Gi
    storageClassName: fast-ssd
    accessModes:
      - ReadWriteOnce
    mountPath: /data
  - name: logs-storage
    size: 5Gi
    storageClassName: standard
    accessModes:
      - ReadWriteOnce
    mountPath: /var/log

Application with PVC in Init Container

replicaCount: 2
image: myapp
imageTag: v1.0.0
persistentVolumeClaims:
  - name: data-storage
    size: 10Gi
    mountPath: /data
initContainers:
  enabled: true
  containers:
    - name: init-migration
      image: myapp
      imageTag: v1.0.0
      command: ["/bin/sh", "-c"]
      args: ["python manage.py migrate"]
      volumeMounts:
        - name: data-storage
          mountPath: /data

Application with PVC in Sidecar Container

replicaCount: 1
image: myapp
imageTag: v1.0.0
persistentVolumeClaims:
  - name: logs-storage
    size: 5Gi
    mountPath: /var/log
extraContainers:
  enabled: true
  containers:
    - name: log-collector
      image: fluent/fluent-bit:latest
      volumeMounts:
        - name: logs-storage
          mountPath: /var/log

Application with Sidecar Container

replicaCount: 1
image: myapp
imageTag: v1.0.0
extraContainers:
  enabled: true
  containers:
    - name: log-collector
      image: fluent/fluent-bit:latest
      volumeMounts:
        - name: varlog
          mountPath: /var/log
volumes:
  - name: varlog
    hostPath:
      path: /var/log

Troubleshooting

Check Pod Status

kubectl get pods -l app.kubernetes.io/name=application

View Pod Logs

kubectl logs -l app.kubernetes.io/name=application

Describe Pod for Events

kubectl describe pod <pod-name>

Check Service Endpoints

kubectl get endpoints <service-name>

Test Ingress

kubectl get ingress
curl -H "Host: example.com" http://<ingress-ip>/

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

Changelog

See CHANGELOG.md for a list of changes and version history.

License

This project is licensed under the MIT License - see the LICENSE file for details.

About

application helm chart

Resources

Readme

License

MIT license
Activity

Stars

0 stars

Watchers

0 watching

Forks

2 forks
Report repository

Releases

No releases published

Packages

 
 
 

Contributors

Languages