Skip to content

Automatically expire stale Pending node entries - #8173

Draft
Amaury Chamayou (achamayou) with Copilot wants to merge 2 commits into
mainfrom
copilot/ccf-6672-node-expire-pending-entries
Draft

Automatically expire stale Pending node entries#8173
Amaury Chamayou (achamayou) with Copilot wants to merge 2 commits into
mainfrom
copilot/ccf-6672-node-expire-pending-entries

Conversation

Copilot AI commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

Unsuccessful join attempts can leave Pending node records requiring manual operator cleanup. This adds configurable, primary-driven expiration.

  • Expiration

    • Persist each Pending node’s admission timestamp.
    • Periodically remove entries older than pending_node_timeout.
    • Remove associated certificates and sealed recovery data.
  • Configuration

    • Default timeout: 24h.
    • Set 0s to disable cleanup.
{
  "pending_node_timeout": "6h"
}
  • Compatibility

    • Initialize timestamps for legacy Pending entries on first inspection.
    • Reset invalid or future timestamps to avoid premature deletion.
    • Preserve timestamps across restart and primary failover.
  • Integration

    • Add host configuration schema and operator documentation.
    • Add focused unit and end-to-end coverage.

Co-authored-by: achamayou <4016369+achamayou@users.noreply.github.com>
Copilot AI changed the title [WIP] Add automatic expiration for KV pending entries after delay Automatically expire stale Pending node entries Aug 18, 2026
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.

Node Pending entries in the KV should automatically expire after a configurable delay

2 participants