Skip to content

Commit 63b6fc9

Browse files
authored
fix(helm): align values-production-example.yaml with values.yaml (#2606)
- Move S3 credentials from secrets.objectStore to s3.auth - Update external PostgreSQL config to use databaseUrl/directUrl approach - Add existingSecret support for PostgreSQL with secretKeys - Add TLS configuration for external Redis - Add existingSecret support for Redis, ClickHouse and S3 - Add complete external S3 configuration example - Improve secure credential management documentation These changes align the production example file with the current values.yaml structure, making it easier to configure external services with better support for secret management.
1 parent aa66462 commit 63b6fc9

File tree

1 file changed

+43
-13
lines changed

1 file changed

+43
-13
lines changed

hosting/k8s/helm/values-production-example.yaml

Lines changed: 43 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -7,10 +7,6 @@ secrets:
77
magicLinkSecret: "YOUR_32_CHAR_HEX_SECRET_HERE_002"
88
encryptionKey: "YOUR_32_CHAR_HEX_SECRET_HERE_003"
99
managedWorkerSecret: "YOUR_32_CHAR_HEX_SECRET_HERE_004"
10-
# Object store credentials (customize for your setup)
11-
objectStore:
12-
accessKeyId: "your-access-key"
13-
secretAccessKey: "your-secret-key"
1410

1511
# Production webapp configuration
1612
webapp:
@@ -95,6 +91,9 @@ s3:
9591
auth:
9692
rootUser: "admin"
9793
rootPassword: "your-strong-s3-password"
94+
# Webapp credentials for S3 access (can be different from root)
95+
accessKeyId: "your-access-key"
96+
secretAccessKey: "your-secret-key"
9897
persistence:
9998
enabled: true
10099
size: 500Gi
@@ -140,22 +139,36 @@ supervisor:
140139
# Example: Use external PostgreSQL instead
141140
# postgres:
142141
# deploy: false
143-
# external:
144-
# host: "your-postgres-host.rds.amazonaws.com"
145-
# port: 5432
146-
# database: "trigger"
147-
# username: "trigger_user"
148-
# password: "your-db-password"
149-
# schema: "public"
142+
# connection:
150143
# sslMode: "require" # Use 'require' or 'verify-full' for production
144+
# external:
145+
# # Database URL configuration - simplified approach using URLs
146+
# databaseUrl: "postgresql://trigger_user:your-db-password@your-postgres-host.rds.amazonaws.com:5432/trigger?schema=public&sslmode=require"
147+
# directUrl: "" # Optional: Direct URL for migrations (if not set, databaseUrl will be used)
148+
# #
149+
# # Optional: Connectivity check configuration during webapp startup
150+
# connectivityCheck:
151+
# host: "your-postgres-host.rds.amazonaws.com:5432"
152+
# #
153+
# # Secure credential management (recommended for production)
154+
# # existingSecret: "postgres-credentials" # Name of existing secret containing DATABASE_URL
155+
# # secretKeys:
156+
# # databaseUrlKey: "postgres-database-url" # Key in existing secret
157+
# # directUrlKey: "postgres-direct-url" # Key in existing secret (optional)
151158

152159
# Example: Use external Redis instead
153160
# redis:
154161
# deploy: false
155162
# external:
156163
# host: "your-redis-cluster.cache.amazonaws.com"
157164
# port: 6379
158-
# password: "your-redis-password"
165+
# password: "your-redis-password" # Optional - ignored if existingSecret is set
166+
# tls:
167+
# enabled: true # Set to true for Redis instances requiring TLS (e.g., AWS ElastiCache)
168+
# #
169+
# # Secure credential management (recommended for production)
170+
# # existingSecret: "redis-credentials" # Name of existing secret containing password
171+
# # existingSecretPasswordKey: "redis-password" # Key in existing secret containing password
159172

160173
# Example: Use external ClickHouse instead
161174
# clickhouse:
@@ -165,5 +178,22 @@ supervisor:
165178
# httpPort: 8443 # Use 8443 for HTTPS
166179
# nativePort: 9440 # Use 9440 for secure native connections
167180
# username: "trigger_user"
168-
# password: "your-clickhouse-password"
181+
# password: "your-clickhouse-password" # Optional - ignored if existingSecret is set
169182
# secure: true # Use true for TLS/secure connections
183+
# #
184+
# # Secure credential management (recommended for production)
185+
# # existingSecret: "clickhouse-credentials" # Name of existing secret containing password
186+
# # existingSecretKey: "clickhouse-password" # Key in existing secret containing password
187+
188+
# Example: Use external S3-compatible storage instead
189+
# s3:
190+
# deploy: false
191+
# external:
192+
# endpoint: "https://s3.amazonaws.com" # or your S3-compatible endpoint
193+
# accessKeyId: "your-access-key"
194+
# secretAccessKey: "your-secret-key"
195+
# #
196+
# # Secure credential management (recommended for production)
197+
# # existingSecret: "s3-credentials" # Name of existing secret containing S3 credentials
198+
# # existingSecretAccessKeyIdKey: "access-key-id" # Key in existing secret containing access key ID
199+
# # existingSecretSecretAccessKeyKey: "secret-access-key" # Key in existing secret containing secret access key

0 commit comments

Comments
 (0)