Skip to content

fix(feed): use dedicated for_you_by_date config for For You time feed#3752

Merged
pnvasanth merged 3 commits intomainfrom
fix/for-you-by-date-feed-config
Mar 30, 2026
Merged

fix(feed): use dedicated for_you_by_date config for For You time feed#3752
pnvasanth merged 3 commits intomainfrom
fix/for-you-by-date-feed-config

Conversation

@pnvasanth
Copy link
Copy Markdown
Contributor

Summary

  • Added ForYouByDate to FeedConfigName enum mapping to for_you_by_date
  • Switched versionToTimeFeedGenerator (For You > By Date) from custom_feed_na_v1 to the new dedicated for_you_by_date feed config

Test plan

  • Updated existing test assertion for feed v2 TIME ranking

@pulumi
Copy link
Copy Markdown

pulumi Bot commented Mar 30, 2026

🍹 The Update (preview) for dailydotdev/api/prod (at 4a50d3a) was successful.

✨ Neo Explanation

This is a standard application deployment rolling out a new build across all services, workers, and cron jobs in the production cluster, accompanied by the usual database and ClickHouse schema migration jobs for the new version.

Root Cause Analysis

A new version of the application has been built and is being deployed to production. Every workload is being updated from the previous build to the latest build, with new database and ClickHouse migration jobs created for the new version.

Dependency Chain

The new application image version cascades uniformly across the entire stack:

  • 7 Deployments (API, background workers, WebSocket, private, temporal, personalized digest, worker jobs) are all being rolled to the new image
  • 38 CronJobs are having their image and version label updated to match
  • 2 one-time migration Jobs (DB migration via TypeORM and ClickHouse migration) are being replaced — the old version's jobs are deleted and new jobs for the current version are created to run schema/data migrations against the new build

Risk Analysis

No stateful resources (databases, storage buckets, persistent volumes) are being replaced or deleted. The migration jobs are the only operationally sensitive step — if either migration fails, the new application pods may misbehave against an un-migrated schema. The Deployments themselves use rolling updates by default, so no downtime is expected. There is also a non-blocking GCP credentials warning that does not affect the Kubernetes changes.

Resource Changes

    Name                                                       Type                           Operation
~   vpc-native-generate-search-invites-cron                    kubernetes:batch/v1:CronJob    update
~   vpc-native-post-analytics-history-day-clickhouse-cron      kubernetes:batch/v1:CronJob    update
~   vpc-native-worker-job-deployment                           kubernetes:apps/v1:Deployment  update
~   vpc-native-clean-zombie-images-cron                        kubernetes:batch/v1:CronJob    update
~   vpc-native-update-achievement-rarity-cron                  kubernetes:batch/v1:CronJob    update
~   vpc-native-update-source-public-threshold-cron             kubernetes:batch/v1:CronJob    update
~   vpc-native-channel-highlights-cron                         kubernetes:batch/v1:CronJob    update
~   vpc-native-clean-expired-better-auth-sessions-cron         kubernetes:batch/v1:CronJob    update
~   vpc-native-validate-active-users-cron                      kubernetes:batch/v1:CronJob    update
~   vpc-native-user-posts-analytics-refresh-cron               kubernetes:batch/v1:CronJob    update
~   vpc-native-channel-digests-cron                            kubernetes:batch/v1:CronJob    update
~   vpc-native-temporal-deployment                             kubernetes:apps/v1:Deployment  update
~   vpc-native-check-analytics-report-cron                     kubernetes:batch/v1:CronJob    update
~   vpc-native-clean-zombie-opportunities-cron                 kubernetes:batch/v1:CronJob    update
~   vpc-native-clean-stale-user-transactions-cron              kubernetes:batch/v1:CronJob    update
~   vpc-native-hourly-notification-cron                        kubernetes:batch/v1:CronJob    update
~   vpc-native-rotate-weekly-quests-cron                       kubernetes:batch/v1:CronJob    update
-   vpc-native-api-clickhouse-migration-12a500e4               kubernetes:batch/v1:Job        delete
+   vpc-native-api-clickhouse-migration-6227ffc6               kubernetes:batch/v1:Job        create
~   vpc-native-clean-zombie-user-companies-cron                kubernetes:batch/v1:CronJob    update
~   vpc-native-daily-digest-cron                               kubernetes:batch/v1:CronJob    update
~   vpc-native-post-analytics-clickhouse-cron                  kubernetes:batch/v1:CronJob    update
~   vpc-native-sync-subscription-with-cio-cron                 kubernetes:batch/v1:CronJob    update
~   vpc-native-rotate-daily-quests-cron                        kubernetes:batch/v1:CronJob    update
-   vpc-native-api-db-migration-12a500e4                       kubernetes:batch/v1:Job        delete
~   vpc-native-clean-channel-highlights-cron                   kubernetes:batch/v1:CronJob    update
~   vpc-native-bg-deployment                                   kubernetes:apps/v1:Deployment  update
~   vpc-native-user-profile-analytics-history-clickhouse-cron  kubernetes:batch/v1:CronJob    update
~   vpc-native-ws-deployment                                   kubernetes:apps/v1:Deployment  update
~   vpc-native-update-source-tag-view-cron                     kubernetes:batch/v1:CronJob    update
~   vpc-native-squad-posts-analytics-refresh-cron              kubernetes:batch/v1:CronJob    update
+   vpc-native-api-db-migration-6227ffc6                       kubernetes:batch/v1:Job        create
~   vpc-native-user-profile-analytics-clickhouse-cron          kubernetes:batch/v1:CronJob    update
~   vpc-native-clean-zombie-users-cron                         kubernetes:batch/v1:CronJob    update
~   vpc-native-user-profile-updated-sync-cron                  kubernetes:batch/v1:CronJob    update
~   vpc-native-deployment                                      kubernetes:apps/v1:Deployment  update
~   vpc-native-update-tags-str-cron                            kubernetes:batch/v1:CronJob    update
~   vpc-native-update-trending-cron                            kubernetes:batch/v1:CronJob    update
~   vpc-native-update-tag-recommendations-cron                 kubernetes:batch/v1:CronJob    update
~   vpc-native-personalized-digest-deployment                  kubernetes:apps/v1:Deployment  update
~   vpc-native-generic-referral-reminder-cron                  kubernetes:batch/v1:CronJob    update
... and 10 other changes

@pnvasanth pnvasanth force-pushed the fix/for-you-by-date-feed-config branch from 31bb9ad to 4a50d3a Compare March 30, 2026 09:14
@pnvasanth pnvasanth merged commit 7519f93 into main Mar 30, 2026
10 checks passed
@pnvasanth pnvasanth deleted the fix/for-you-by-date-feed-config branch March 30, 2026 09:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant