-
Notifications
You must be signed in to change notification settings - Fork 138
Document the remote-jobs opt-in and MDM keys #914
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -8,6 +8,10 @@ Remote Jobs allow administrators to trigger actions on connected peers without r | |
| Remote Jobs require the target peer to be **online** and running **NetBird v0.64.0 or later**. | ||
| </Note> | ||
|
|
||
| <Note> | ||
| Remote Jobs are **opt-in on the peer** and disabled by default. A peer accepts remote jobs only when started with `--allow-remote-jobs`, or when the `allowRemoteJobs` [MDM policy](/client/mdm-integration) is set. Enabling it is a privileged operation on the client (like enabling the embedded SSH server). Peers that have not opted in report this to Management, and the Dashboard disables the **Run Remote Job** button for them. | ||
| </Note> | ||
|
Comment on lines
+11
to
+13
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win State that the MDM policy must be
Proposed fix- ... when the `allowRemoteJobs` MDM policy is set.
+ ... when `allowRemoteJobs` is set to `true` in the MDM policy.
...
-- The target peer must have **opted into remote jobs** (`--allow-remote-jobs` or the `allowRemoteJobs` MDM policy)
+- The target peer must have **opted into remote jobs** (`--allow-remote-jobs` or `allowRemoteJobs: true` in the MDM policy)Also applies to: 146-146 🤖 Prompt for AI Agents |
||
|
|
||
| ## Overview | ||
|
|
||
| Remote Jobs are managed per-peer and follow a simple lifecycle: | ||
|
|
@@ -57,6 +61,8 @@ The Debug Bundle job remotely collects diagnostic information from a peer, inclu | |
| | Log File Count | Number of log files to include | 1 - 1000 | 10 | | ||
| | Bundle Duration | Time period to collect logs before creating the bundle | 1 - 5 minutes | Disabled | | ||
| | Anonymize | Remove sensitive information (IP addresses, domains, etc.) | On / Off | Off | | ||
| | Anonymization Level | With Anonymize on, `default` keeps internal (private) IP ranges readable; `strict` also anonymizes private, CGNAT and link-local addresses | `default` / `strict` | `default` | | ||
| | Upload URL | Upload service the peer requests an upload URL from (must be an `https` URL). A peer with the `debugBundleUploadURL` [MDM policy](/client/mdm-integration) set overrides this value | https URL | Default upload server | | ||
|
|
||
| **Result:** | ||
|
|
||
|
|
@@ -81,7 +87,7 @@ On success, the job returns an **upload key** that can be used to retrieve the d | |
| </p> | ||
|
|
||
| <Note> | ||
| The **Run Remote Job** button is disabled when the peer is offline or when you lack the required permissions. | ||
| The **Run Remote Job** button is disabled when the peer is offline, when the peer has not opted into remote jobs, or when you lack the required permissions. | ||
| </Note> | ||
|
|
||
| ### Viewing Job History | ||
|
|
@@ -137,6 +143,7 @@ curl https://api.netbird.io/api/peers/{peerId}/jobs/{jobId} \ | |
| ## Limitations | ||
|
|
||
| - The target peer must be **online and connected** to the management server | ||
| - The target peer must have **opted into remote jobs** (`--allow-remote-jobs` or the `allowRemoteJobs` MDM policy) | ||
| - Only **one pending job** per peer at a time | ||
| - Peers must be running **NetBird v0.64.0 or later** | ||
| - Jobs time out after **5 minutes** if the peer does not respond | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Update the policy count.
The preceding text at Line 63 says that the reference contains 16 keys, but the table now contains 20 rows, including these two new keys. Remove the hard-coded count or update it so administrators are not given incorrect documentation.
Proposed fix
🤖 Prompt for AI Agents