Repository navigation
Release v1.6.0 - #9
Open
rdwr-egore wants to merge 17 commits into
Open
rdwr-egore wants to merge 17 commits into
rdwr-egore wants to merge 17 commits into
Conversation
rdwr-egore
marked this pull request as ready for review
October 14, 2026 19:12
Review findings corrected; 108 local tests and GitHub CI run 38630917676 passed.
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.
Container Alert v1.6.0 release candidate (since v1.5.4)
Status: Open release candidate; not merged, tagged, published, or deployed. The
VERSIONfile remains1.6.0. Full inventory: v1.6.0 release notes.Included changes
PR Beta #3 — reliability and installer hardening, concurrent state save, bounded manual exec probes, post-reboot summary.
PR fix: Rate-limit removed container event warnings and resolve by ID #6 — event-ID resolution, name reuse, rate-limited removed-container warnings.
PR fix: Deduplicate restart-loop alerts and require stable recovery #5 — authoritative Docker RestartCount, restart-loop deduplication, stable recovery.
PR fix: Correlate planned Docker stops before reporting crashes #7 — intentional stop correlation, SIGKILL exit-137 vs confirmed OOM.
PR feat: Optional HA active-node change alert (draft) #4 — optional independent HA active-node detection using promoted HA Operator.
PR docs: clarify unreleased changes and image versioning #8 — release documentation/version clarification.
PR Fix notification consistency and Syslog alert priorities for v1.6 #10 — notification field/priority consistency and Syslog retention at local WARNING/ERROR.
Release branch — stable recovery for crashes/OOM even after external restarts, while preserving the incident state machine and HA logic.
Customer communication — approved messages for CRASH/OOM/UNHEALTHY/RESTART-LOOP/RECOVERED/REBOOT-SUMMARY and fallback; retain HA-FAILOVER advice unchanged. Email/Slack human-facing label is
Context; compatibility-preserving Syslogaction=, event IDs, MIB and severity mapping unchanged. CRASH retains the read-onlydocker logsdiagnostic; no instructions to modify Compose, resource limits, or other production settings.Critical test safety — removed live/shared-engine destructive testing path and unsafe host-based README exercises. Release smoke runs exclusively on an ephemeral GitHub-hosted runner, with an empty, uniquely labelled, localhost-only disposable Docker Engine; tests must fail closed otherwise. All cleanup verifies test labels and leftovers. No operational Docker workloads are touched by this workflow.
Single installer — every operator receives the same complete versioned package (installer + prebuilt image + checksum). Run bash install.sh; no Internet, Git, source build or online/offline choice needed on the target. Existing settings stay in place; only the watchdog is recreated.
Release packaging — after approval and tagging on main, hosted CI builds the versioned image and publishes exactly two assets: container-alert-v.tar.gz and SHA256SUMS. Assets are uploaded to a draft, checked, and only then published.
Documentation audit and navigation — one customer Installation and Operations guide + versioned release notes in docs/customer; developer/release workflows, HA design, historical QA and evidence isolated under docs/engineering. The old duplicate DEPLOYMENT_ADVANCED file was removed after preserving its SNMP integration and technical content. Release package includes customer documentation only.
Runtime acceptance — commit
136ce0a(October 15, 2026)node A → node B → node A, correctly generated one WARNING on the newly active node. This is historical lab evidence from an earlier v1.6 candidate; no new HA operation was performed for this text/safety update.Documentation/privacy update: Commit
7077dferemoves lab-specific hostnames, addresses, and identifiers from the tracked release documentation, JSON evidence, configuration examples, and tests. It also simplifies customer-facing verification. The privacy cleanup was validated at that commit. No runtime monitoring logic was changed.Current release validation — commit 3ae5a0e (October 16, 2026)
Complete documentation audit — commit 43b0d44 (October 16, 2026)
Release gates and limitations
End-to-end SMTP, Slack and SNMP delivery to real customer destinations were not all verified; the earlier user-requested SMTP timeout exception remains. No destructive cluster host reboot, STONITH or network-partition tests were performed. An external lab Docker restarter was observed historically, but its initiator was not identified.
Safety advisory: Earlier nested-engine testing on a shared host triggered real watchdog notifications. Destructive acceptance must run only on disposable hosted CI, never on shared or operational hosts.