CloudNativePG 1.26+ supports declarative PostgreSQL major version upgrades.
Upgrading from chart v0.23.0 (operator 1.25.0) to v0.27.0.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
TeslaMate 2.2.0 requires PostgreSQL 17.3+ for the 17.x series.
Upgrading to PostgreSQL 18 instead of minor version bump.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
TeslaMate migrations need to create/drop PostgreSQL extensions
(cube, earthdistance) which requires superuser privileges.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
The password contains @ characters which break URL parsing.
TeslaMate supports separate DATABASE_USER/PASS/NAME/HOST variables.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Use explicit TeslaMate version v2.2.0 instead of :latest
- Remove redundant "Manual sync only" comments from all app manifests
Note: borgmatic user already has pg_read_all_data role which grants
SELECT on all tables in all databases, so no grant updates needed.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Add TeslaMate k8s deployment with Tailscale ingress at tesla.tail8d86e.ts.net
- Add teslamate user to CloudNativePG blumeops-pg cluster
- Add TeslaMate PostgreSQL datasource to Grafana
- Import 18 TeslaMate Grafana dashboards for charging, drives, efficiency, etc.
- Add teslamate database to borgmatic backup configuration
- Create 1Password-templated secrets for encryption key and DB credentials
Requires user action before deployment:
1. Create 1Password items: "TeslaMate DB Password" and "TeslaMate Encryption Key"
2. Apply secrets via op inject
3. Create teslamate database manually
See argocd/manifests/teslamate/README.md for deployment instructions.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>