[GH-ISSUE #4634] Feature Request: Enhance Client Version Posture Check with Dynamic latest, n-1 support #9918

Open
opened 2026-08-05 01:23:57 -04:00 by saavagebueno · 4 comments
Owner

Originally created by @Br00dkast on GitHub (Oct 14, 2025).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/4634

The current "NetBird Client Version" posture check is an excellent feature for ensuring clients meet a minimum security baseline. However, it requires a static version string (e.g., 0.28.1) to be entered manually.

The implementation could involve a choice in the UI between "Static Version" (the current behavior) and a new "Dynamic Version" mode. When "Dynamic Version" is selected, the admin could choose from a dropdown:

  • latest (or n): Enforces the absolute latest stable version. A peer is only considered compliant if its version matches the latest official release.

  • latest - 1 (or n-1): Enforces that a peer's version is either the latest stable release or the one immediately preceding it. This is a critical option for allowing a graceful update period for users.

  • latest - 2 (or n-2): Enforces that a peer's version is within the last three stable releases (latest, latest-1, or latest-2).

Originally created by @Br00dkast on GitHub (Oct 14, 2025). Original GitHub issue: https://github.com/netbirdio/netbird/issues/4634 The current "NetBird Client Version" posture check is an excellent feature for ensuring clients meet a minimum security baseline. However, it requires a static version string (e.g., 0.28.1) to be entered manually. The implementation could involve a choice in the UI between "Static Version" (the current behavior) and a new "Dynamic Version" mode. When "Dynamic Version" is selected, the admin could choose from a dropdown: - latest (or n): Enforces the absolute latest stable version. A peer is only considered compliant if its version matches the latest official release. - latest - 1 (or n-1): Enforces that a peer's version is either the latest stable release or the one immediately preceding it. This is a critical option for allowing a graceful update period for users. - latest - 2 (or n-2): Enforces that a peer's version is within the last three stable releases (latest, latest-1, or latest-2).
saavagebueno added the feature-request label 2026-08-05 01:23:57 -04:00
Author
Owner

@ressys1978 commented on GitHub (Oct 14, 2025):

Ohhh...I really like this one.

<!-- gh-comment-id:3402003447 --> @ressys1978 commented on GitHub (Oct 14, 2025): Ohhh...I really like this one.
Author
Owner

@reickbao commented on GitHub (Oct 15, 2025):

yes , it is good idea , makes config stable

<!-- gh-comment-id:3404818474 --> @reickbao commented on GitHub (Oct 15, 2025): yes , it is good idea , makes config stable
Author
Owner

@sahps commented on GitHub (Oct 29, 2025):

Duplicate of https://github.com/netbirdio/netbird/issues/2970

<!-- gh-comment-id:3461657024 --> @sahps commented on GitHub (Oct 29, 2025): Duplicate of https://github.com/netbirdio/netbird/issues/2970
Author
Owner

@PizzaLovingNerd commented on GitHub (May 27, 2026):

Closing, duplicate of #2970.

<!-- gh-comment-id:4560234488 --> @PizzaLovingNerd commented on GitHub (May 27, 2026): Closing, duplicate of #2970.
Sign in to join this conversation.
No Label feature-request
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#9918