Integrate banjo-utils for health probes and migrate helm chart#23
Merged
Conversation
thenav56
force-pushed
the
feat/banjo-helm-migration
branch
3 times, most recently
from
675f988 to
ec9bb4c
Compare
…r_resources) Add banjo-utils (branch pin feature/health-endpoints) and wire its health tooling, replacing the homegrown wait_for_resources command: - INSTALLED_APPS += banjo_utils; HealthProbeMiddleware first (serves pod-local /healthz/live/ and /healthz/ready/, bypassing ALLOWED_HOSTS). - BANJO_HEALTH_PROBE_* settings; setup_worker_heartbeat(app) in celery for the banjo-celery-probe worker/beat liveness. - Sentry traces_sampler ignores health-probe paths so probes don't burn quota. - LOGGING CallbackFilter drops /healthz/* request-line noise from django.server (dev) and gunicorn.access (prod). - Delete common wait_for_resources (and its RetryHelper) in favour of banjo's; CI docker__wait_cmd --redis -> --cache to match banjo's renamed flag. - Keep django-health-check (/health-check/) as the external UptimeRobot monitor.
…-dev3 Values-schema migration (dependency alias kept as `app`): - Drop bundled subcharts (postgresql/minio/redis/rabbitmq); infra is supplied externally (alpha DB/S3/cache secrets come from user-provided secrets). - ingress -> api.ingress; argoHook.hooks -> hooks.jobs (hook: Sync + sync-waves 10/20/25, wait-for-resources gates db-migrate/collect-static); worker.beat -> worker.addons.beat (Recreate); queueCommandPrefix / queueDefaultResources -> queueDefaults.*; operators extraEnvVars list -> env map (DragonflyDB kept via extraManifests). - db-migrate/collect-static inherit chart defaults; only wait-for-resources overrides the command (--db --cache [--minio]). - alpha create-users uses the hooks `files` mechanism (dev3): script mounted via a per-job ConfigMap at /etc/hook-files and piped into `manage.py shell`. - Enable probes in base values: api /healthz/*, worker/beat banjo-celery-probe heartbeat (RAM emptyDir); omit replicaCount (no KEDA). - Regenerate alpha-1 + staging snapshots; helm template renders both.
Stock django_celery_beat DatabaseScheduler never touches the beat heartbeat file, so BANJO_CELERY_HEARTBEAT_FILE had no writer and the banjo-celery-probe liveness check always saw a missing/stale file. setup_worker_heartbeat only wires the worker bootstep, not beat. Switch beat's --scheduler to the heartbeat-aware subclass and regenerate snapshots.
thenav56
force-pushed
the
feat/banjo-helm-migration
branch
from
a5ce686 to
e5fc5d7
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes
This PR doesn't introduce any:
printThis PR contains valid: