docs: align cronjob nodepool docs with required affinity behavior#116
Open
docs: align cronjob nodepool docs with required affinity behavior#116
Conversation
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
qovery-doc-mintlify-proxy | ff086fa | May 07 2026, 10:17 AM |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Cron job pod affinity for the dedicated cronjob Karpenter nodepool was recently switched from preferred (soft) to required (hard) so cron pods actually land on that nodepool instead of silently scheduling on the default nodepool whenever it has spare capacity. The docs still described the previous soft behavior. Both the cronjob page and the EKS managed cluster resources page now: * describe a required (hard) node affinity instead of preferred * state that redeploying cron jobs is mandatory after enabling or disabling the cronjob nodepool, not just recommended * remove the false claim that jobs fall back to the default nodepool when the cronjob nodepool is removed; with hard affinity they stay in Pending until redeployed Pairs with the corresponding engine code change.
Guimove
force-pushed
the
docs/cronjob-required-affinity
branch
from
0ee7462 to
ff086fa
Compare
benjaminch
approved these changes
May 7, 2026
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
2 participants
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.
Summary
Cron job pod affinity for the dedicated
cronjobKarpenter nodepool was recently switched from preferred (soft) to required (hard) so cron pods actually land on that nodepool instead of silently scheduling ondefaultwhenever it has spare capacity. This PR aligns the docs with the new behavior.Files updated
docs/configuration/cronjob.mdxdocs/configuration/integrations/kubernetes/eks/managed.mdxWhat changed
Pendinguntil redeployed.Why
The previous wording described soft (preferred) affinity behavior, including a fallback that no longer exists. Without this update, anyone toggling the setting without redeploying could be surprised by cron jobs stuck in
Pending.