Follow-up from #194 (reporter's stood-behind suggestion 3).
k8s_sync_enabled and k8s_sync_interval_seconds exist on the cluster model, schemas and serializer dicts, but have no reader anywhere outside those: celery_app.py adds no beat entry, so an operator can set them, get a 200, and nothing happens — no periodic sync is scheduled.
PR #200 stamps last_synced_at on scans that genuinely reach the cluster (the core #194 fix) but deliberately does NOT implement periodic auto-sync. This issue tracks wiring k8s_sync_enabled/k8s_sync_interval_seconds to an actual Celery beat schedule (or equivalent) so the settings take effect.
Relates to #194.
https://claude.ai/code/session_01UCsZXDxBsWV2s4kT47DwDW
Follow-up from #194 (reporter's stood-behind suggestion 3).
k8s_sync_enabledandk8s_sync_interval_secondsexist on the cluster model, schemas and serializer dicts, but have no reader anywhere outside those:celery_app.pyadds no beat entry, so an operator can set them, get a 200, and nothing happens — no periodic sync is scheduled.PR #200 stamps
last_synced_aton scans that genuinely reach the cluster (the core #194 fix) but deliberately does NOT implement periodic auto-sync. This issue tracks wiringk8s_sync_enabled/k8s_sync_interval_secondsto an actual Celery beat schedule (or equivalent) so the settings take effect.Relates to #194.
https://claude.ai/code/session_01UCsZXDxBsWV2s4kT47DwDW