## Summary - Deploy miniflux in k8s via ArgoCD - Expose via Tailscale Ingress at feed.tail8d86e.ts.net - Retire brew PostgreSQL (no longer needed) - Rename k8s-pg to pg (canonical hostname) - Remove ansible miniflux and postgresql roles - Update borgmatic to backup pg.tail8d86e.ts.net - Update all zk documentation ## Deployment and Testing - [x] Miniflux pod running in k8s - [x] User login works at https://feed.tail8d86e.ts.net - [x] Feeds and entries visible - [x] brew miniflux and postgresql stopped - [x] Tailscale services migrated (feed, pg) - [x] zk documentation updated - [x] Run ansible to apply role removals - [ ] Verify borgmatic backup with new pg hostname 🤖 Generated with [Claude Code](https://claude.com/claude-code) Reviewed-on: https://forge.tail8d86e.ts.net/eblume/blumeops/pulls/33
13 lines
620 B
Smarty
13 lines
620 B
Smarty
# Miniflux database connection secret
|
|
#
|
|
# The miniflux user password is auto-generated by CloudNativePG and stored in
|
|
# blumeops-pg-app secret in the databases namespace. To create this secret:
|
|
#
|
|
# 1. Get the URI from CNPG secret:
|
|
# kubectl -n databases get secret blumeops-pg-app -o jsonpath='{.data.uri}' | base64 -d
|
|
#
|
|
# 2. Create the secret (one-liner):
|
|
# kubectl create secret generic miniflux-db -n miniflux \
|
|
# --from-literal=url="$(kubectl -n databases get secret blumeops-pg-app -o jsonpath='{.data.uri}' | base64 -d)"
|
|
#
|
|
# Note: Uses internal k8s DNS hostname (blumeops-pg-rw.databases) not Tailscale
|