Fix chart issues from PR #19 review: redis key path bug, stale docs, missing changelog entry

CHANGELOG.md

@@ -68,6 +68,15 @@ For users upgrading to v1.1.0:
 ### Changed
 - Improved default volume configuration
 
+## [1.0.3] - 2024
+
+### Added
+- **Autoscaling Support**: Added Horizontal Pod Autoscaler (HPA) configuration via `autoscaling` values
+- Node selector, tolerations, and affinity configuration support
+
+### Changed
+- Improved deployment configuration for better Kubernetes scheduling control
+
 ## [1.0.2] - 2024
 
 ### Added

README.md

@@ -293,7 +293,7 @@ This guide explains how to deploy Temporal in the same Kubernetes cluster for us
 
 ### Architecture
 
-```
+```text
 ┌─────────────────────────────────────────────────┐
 │         Temporal Namespace (temporal)            │
 ├─────────────────────────────────────────────────┤
@@ -510,7 +510,7 @@ helm upgrade postiz-app oci://ghcr.io/gitroomhq/postiz-helmchart/charts/postiz-a
   --reuse-values
 ```
 
-See [Migration from v1.1.0](#migration-from-v110-embedded-temporal) for detailed upgrade instructions.
+See [Migration from v1.1.0](#to-110) for detailed upgrade instructions.
 
 ### To 1.0.0
 

charts/postiz/README.md

@@ -26,7 +26,7 @@ This chart bootstraps a [Postiz](https://postiz.com) deployment on a Kubernetes
 
 - Kubernetes 1.19+
 - Helm 3.8+
-- PV provisioner support in the underlying infrastructure (for PostgreSQL/Redis persistence)
+- PV provisioner support in the underlying infrastructure (for PostgreSQL/Valkey persistence)
 
 ## Installing the Chart
 
@@ -108,11 +108,11 @@ helm install postiz oci://ghcr.io/gitroomhq/postiz-helmchart/charts/postiz-app -
 
 ### Temporal Workflow Engine
 
-| Parameter                      | Description              | Default |
-| ------------------------------ | ------------------------ | ------- |
-| `temporal.enabled`             | Deploy Temporal          | `true`  |
-| `temporal.server.replicaCount` | Temporal server replicas | `1`     |
-| `temporal.web.enabled`         | Deploy Temporal Web UI   | `true`  |
+Temporal is required and must be deployed separately. Configure the address via `env.TEMPORAL_ADDRESS`.
+
+| Parameter              | Description                              | Default |
+| ---------------------- | ---------------------------------------- | ------- |
+| `env.TEMPORAL_ADDRESS` | **REQUIRED** Temporal frontend address   | `""`    |
 
 ### Secrets & Auto-Generation
 
@@ -175,17 +175,9 @@ postgresql:
       memory: "256Mi"
       cpu: "250m"
 
-temporal:
-  enabled: true
-  server:
-    replicaCount: 3
-    config:
-      persistence:
-        numHistoryShards: 512
-    resources:
-      requests:
-        memory: "1Gi"
-        cpu: "500m"
+env:
+  # REQUIRED: Configure your Temporal deployment address
+  TEMPORAL_ADDRESS: "temporal-frontend.temporal.svc.cluster.local:7233"
 
 secrets:
   autoGenerate:
@@ -234,31 +226,13 @@ secrets:
 
 ### Temporal with External Database
 
-```yaml
-temporal:
-  enabled: true
-  server:
-    config:
-      persistence:
-        datastores:
-          default:
-            sql:
-              pluginName: postgres12
-              host: "temporal-db.example.com"
-              port: 5432
-              user: "temporal"
-              password: "temporal-password"
-              databaseName: "temporal"
-              maxConns: 20
-              maxIdleConns: 5
-          visibility:
-            sql:
-              pluginName: postgres12
-              host: "temporal-db.example.com"
-              port: 5432
-              user: "temporal"
-              password: "temporal-password"
-              databaseName: "temporal_visibility"
+Temporal is deployed separately from this chart. To configure Temporal to use an external database, use the [temporal-self-hosted.yaml](../../examples/temporal-self-hosted.yaml) example as a reference when installing the `temporalio/temporal` chart:
+
+```bash
+helm install temporal temporalio/temporal \
+  --namespace temporal \
+  --create-namespace \
+  --values examples/temporal-self-hosted.yaml
 ```
 
 ### External Secrets with Vault

charts/postiz/templates/_helpers.yaml

@@ -98,7 +98,7 @@ Generate Redis/Valkey connection URL with properly encoded credentials
 {{- if .Values.redis.enabled -}}
 {{- $password := .Values.redis.auth.password | urlquery -}}
 {{- $host := include "postiz.redisHost" . -}}
-{{- $port := .Values.redis.master.service.ports.redis | default 6379 -}}
+{{- $port := .Values.redis.primary.service.ports.redis | default 6379 -}}
 {{- if $password -}}
 {{- printf "redis://default:%s@%s:%d" $password $host ($port | int) -}}
 {{- else -}}

charts/postiz/templates/extramanifests.yaml

@@ -3,8 +3,8 @@
 ---
 {{- end }}
 {{- if typeIs "string" $manifest }}
-{{ $manifest }}
+{{ $manifest | trim }}
 {{- else }}
-{{ toYaml $manifest }}
+{{ toYaml $manifest | trim }}
 {{- end }}
 {{- end }}

charts/postiz/values.yaml

@@ -118,22 +118,24 @@ tolerations: []
 affinity: {}
 
 # PostgreSQL configuration
+# IMPORTANT: Change auth.password for production deployments
 postgresql:
   enabled: true
   auth:
     username: postiz
-    password: postiz-password
+    password: postiz-password  # Change this for production!
     database: postiz
   service:
     ports:
       postgresql: 5432
 
 # Redis/Valkey configuration
 # Note: As of v1.1.0, uses Valkey (Redis fork) for Redis-compatible caching
+# IMPORTANT: Change auth.password for production deployments
 redis:
   enabled: true
   auth:
-    password: postiz-redis-password
+    password: postiz-redis-password  # Change this for production!
   primary:
     service:
       ports: