Repository navigation
Conversation
saltas888
added a commit
to opsmill/infrahub
that referenced
this pull request
Oct 11, 2026
…mits The implementation report records the 11 Oct run of quickstart Part 1 steps 5 and 6 on a dev stack, and the test runs of T061 and T062. T050 is ticked with opsmill/infrahub-helm#100, a draft until the chart's images move to Infrahub 1.13. The report's commit IDs point at the commits of the stack as it is now. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
saltas888
added a commit
to opsmill/infrahub
that referenced
this pull request
Oct 13, 2026
…mits The implementation report records the 11 Oct run of quickstart Part 1 steps 5 and 6 on a dev stack, and the test runs of T061 and T062. T050 is ticked with opsmill/infrahub-helm#100, a draft until the chart's images move to Infrahub 1.13. The report's commit IDs point at the commits of the stack as it is now. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
saltas888
added a commit
to opsmill/infrahub
that referenced
this pull request
Oct 14, 2026
…mits The implementation report records the 11 Oct run of quickstart Part 1 steps 5 and 6 on a dev stack, and the test runs of T061 and T062. T050 is ticked with opsmill/infrahub-helm#100, a draft until the chart's images move to Infrahub 1.13. The report's commit IDs point at the commits of the stack as it is now. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
saltas888
force-pushed
the
task-manager-retention-infp-507
branch
from
October 14, 2026 13:27
cdad2d6 to
72c0791
Compare
…ugh infrahub Infrahub 1.13 adds three task manager retention settings, read from INFRAHUB_TASK_MANAGER_RETENTION_TASK_HISTORY (default 30d), INFRAHUB_TASK_MANAGER_RETENTION_ACTIVITY_LOG (default 7d) and INFRAHUB_TASK_MANAGER_RETENTION_PREFECT_OWN_EVENTS (default 7d). They must reach the task manager container and, when Prefect's background services run in a pod of their own, that container too. Set them in prefect-server.global.prefect.env, the one env list that prefect-helm renders into both the server and the background services containers. server.env and backgroundServices.env would not work: the enterprise values and its config presets replace those lists, and Helm replaces lists instead of merging them. The small, medium, medium-data, large and large-data presets start the separate background services pod with `prefect server services start`, which does not read the retention settings, so it would not delete old task runs and would keep events for Prefect's default retention. Start it with `infrahub tasks background-services` instead, which loads the Infrahub configuration, applies the retention to Prefect's settings and then runs the same services. The wait loop before it is unchanged. The new command exists only from Infrahub 1.13 on, and the presets run the image set by prefect-server.global.prefect.image.prefectTag, so this change must not be released before that tag points to 1.13. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
saltas888
added a commit
to opsmill/infrahub
that referenced
this pull request
Oct 27, 2026
…mits The implementation report records the 11 Oct run of quickstart Part 1 steps 5 and 6 on a dev stack, and the test runs of T061 and T062. T050 is ticked with opsmill/infrahub-helm#100, a draft until the chart's images move to Infrahub 1.13. The report's commit IDs point at the commits of the stack as it is now. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
saltas888
force-pushed
the
task-manager-retention-infp-507
branch
from
October 27, 2026 22:07
72c0791 to
472f126
Compare
3 of 5 tasks
saltas888
added a commit
to opsmill/infrahub
that referenced
this pull request
Oct 28, 2026
…mits The implementation report records the 11 Oct run of quickstart Part 1 steps 5 and 6 on a dev stack, and the test runs of T061 and T062. T050 is ticked with opsmill/infrahub-helm#100, a draft until the chart's images move to Infrahub 1.13. The report's commit IDs point at the commits of the stack as it is now. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Why
Separate background services must apply Infrahub's retention settings before starting Prefect. Starting them directly with
prefect server services startignores those settings: finished task history remains unbounded and activity events follow Prefect's default retention.This accompanies Infrahub #11289.
Changes
infrahub tasks background-services, including deployments without a sizing preset. The five Enterprise presets use the same command after their existing wait loop.prefect-server.global.prefect.envsupplies both containers with defaults of 30 days for task history, 7 days for Infrahub activity, and 2 days for Prefect internal events, including heartbeats./tmpdirectory for Prometheus metric files.Enterprise availability and edition-specific restrictions remain undecided. The current implementation has no edition gate.
The upgrade job only prints task-history size and cleanup guidance. Operators start backlog cleanup separately with
infrahub tasks flush flow-runs [--rewrite].Validation
Rendered twelve cases using Helm v3.19's chart dependency processing and rendering engine with Prefect chart
2026.10.21032730: Community and Enterprise bases, separate services without presets, all five Enterprise presets, OpenShift variants and custom overrides. Checked the startup arguments, retention environment and writable metrics directory; per-service overrides retain precedence.The scratch Enterprise chart used this branch's Community chart, with unrelated service dependencies disabled. Regenerated the README with helm-docs 1.14.2. No Kubernetes deployment or database cleanup ran.
Release coordination
Do not merge until the Infrahub images move to 1.13 or newer. The chart still selects 1.11.9, which lacks the new command. This requirement applies to all separate-service deployments, including presets.
The Enterprise chart must also move from Community dependency 4.35.0 to the release containing these changes. The chart currently adds no version guard; decide whether to reject older images explicitly before release.