infra/stacks/postiz
Viktor Barzin 61f7539de2 postiz: disable unused providers + pin temporal vs Keel force-policy
Two changes in one commit because they are coupled — the DISABLED_PROVIDERS
addition cannot land safely without the Keel exclusion on temporal:

1. Add DISABLED_PROVIDERS env on postiz Helm chart. Live DB audit showed
   only 'instagram-standalone' connected; all other Postiz providers
   were idle-polling Temporal task queues. List excludes x, linkedin,
   reddit, threads, youtube, tiktok, pinterest, dribbble, slack,
   discord, mastodon, bluesky, lemmy, warpcast, vk, beehiiv, telegram,
   wordpress, nostr, farcaster. Keeps facebook + instagram + the
   standalone variant active.

2. temporal deployment needs keel.sh/policy=never (set live via kubectl
   annotate). Keel was rolling temporalio/auto-setup 1.28.1 -> 0.20.0
   on every helm reconcile because :0.20.0 is published in the same
   registry path but is a DIFFERENT (legacy Cassandra-based) image
   stream. Memory id 1933 trap; new variant captured in id 2315-2319.

   The annotation is set live (not in TF) because the existing TF block
   has lifecycle.ignore_changes = [keel.sh/policy] so the chart
   reconcile won't reset it. Long-term fix: add temporal to the
   Kyverno keel-mutate-existing exclude list so it survives a
   namespace re-label.
2026-05-22 14:17:00 +00:00
..
modules/postiz postiz: disable unused providers + pin temporal vs Keel force-policy 2026-05-22 14:17:00 +00:00
main.tf add postiz + instagram-poster stacks for IG Stories pipeline 2026-05-10 11:12:37 +00:00
secrets add postiz + instagram-poster stacks for IG Stories pipeline 2026-05-10 11:12:37 +00:00
terragrunt.hcl add postiz + instagram-poster stacks for IG Stories pipeline 2026-05-10 11:12:37 +00:00