• Add extraContainers / extraInitContainers for sidecars and init containers on the web Deployment
  
• Add migrationJob.extraInitContainers and migrationJob.extraContainers for the migration Job
  
  • Note: a long-running sidecar in migrationJob.extraContainers will block Job completion; use Kubernetes native sidecars (restartPolicy: Always on init containers, k8s >= 1.29) if needed
    
• GlitchTip 6.2.0
  
• (Breaking) Remove the dedicated worker deployment. The worker is now always embedded in the web ASGI process.
  
  • Remove the entire worker.* values section (including worker.enabled, worker.replicaCount, worker.resources, worker.autoscaling, worker.database, etc.).
    
  • Remove web.embedWorker — GLITCHTIP_EMBED_WORKER=true is always set on the web container.
    
  • If you relied on a separate database user for partition management via worker.database.existingSecret, use glitchtip.maintenanceDatabase.existingSecret instead (applied via MAINTENANCE_DATABASE_URL).
    
• (Breaking) Flatten the web.* values section to the chart root. With only one deployable left, the web. prefix was just noise.
  
  • web.replicaCount → replicaCount
    
  • web.resources → resources
    
  • web.autoscaling → autoscaling
    
  • web.budget → budget
    
  • web.affinity / nodeSelector / tolerations / podAnnotations → root
    
  • web.livenessProbe / readinessProbe / lifecycle / terminationGracePeriodSeconds → root
    
  • web.port → port
    
  • web.service → service
    
  • web.ingress → ingress
    
  • web.extraEnvVars → extraEnvVars (replaces the old shared-across-components root extraEnvVars; use migrationJob.extraEnvVars for migrate-job-only vars)
    
• (Breaking) Drop migrationJob.database. The migrate job now reads MAINTENANCE_DATABASE_URL from glitchtip.maintenanceDatabase.existingSecret (shared with the embedded worker's partition management) and falls back to DATABASE_URL when unset — which is fine for small setups where the app user has DDL.
  
• Default image.tag to Chart.AppVersion. Chart upgrades now pin the matching GlitchTip release automatically; set image.tag explicitly to override. The migrate job and helm test pod previously had no default at all and now share this behavior.
  
• Chart.yaml appVersion is no longer v-prefixed (6.1.4, not v6.1.4) so it matches the GlitchTip Docker tag directly.