starred/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-01-11 20:00:28 +01:00
Code Issues 98 Packages Projects Releases 10 Wiki Activity

[PR #675] [MERGED] Make tailnet updates check interval configurable #1563

New Issue
Closed
opened 2025-12-29 02:30:35 +01:00 by adam · 0 comments
adam commented 2025-12-29 02:30:35 +01:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/juanfont/headscale/pull/675
Author: @juanfont
Created: 7/12/2022
Status: ✅ Merged
Merged: 7/12/2022
Merged by: @juanfont

Base: main ← Head: configurable-update-interval

📝 Commits (4)

  • cf3fc85 Make tailnet updates check configurable
  • 8e0939f Updated changelog
  • 5b5298b Renamed config param for node update check internal
  • 4ccff8b Added the new parameter to the integration test params

📊 Changes

9 files changed (+30 additions, -5 deletions)

View changed files

📝 CHANGELOG.md (+1 -2)
📝 config-example.yaml (+6 -0)
📝 config.go (+16 -0)
📝 integration_test/etc/alt-config.dump.gold.yaml (+1 -0)
📝 integration_test/etc/alt-config.yaml (+1 -0)
📝 integration_test/etc/config.dump.gold.yaml (+1 -0)
📝 integration_test/etc/config.yaml (+1 -0)
📝 integration_test/etc_embedded_derp/config.yaml (+1 -0)
📝 poll.go (+2 -3)

📄 Description

A user with >150 machines in their tailnet reported high CPU consumption. Although for sure we have other bottlenecks, a 10 second check interval for updates might be a bit too much.

This PR allows an advanced user to change this (until now hardcoded) setting.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/juanfont/headscale/pull/675 **Author:** [@juanfont](https://github.com/juanfont) **Created:** 7/12/2022 **Status:** ✅ Merged **Merged:** 7/12/2022 **Merged by:** [@juanfont](https://github.com/juanfont) **Base:** `main` ← **Head:** `configurable-update-interval` --- ### 📝 Commits (4) - [`cf3fc85`](https://github.com/juanfont/headscale/commit/cf3fc85196e13e52db055dbc594d437dcc9765ac) Make tailnet updates check configurable - [`8e0939f`](https://github.com/juanfont/headscale/commit/8e0939f403147f7cb5c3f294e0df6ea6f76d1688) Updated changelog - [`5b5298b`](https://github.com/juanfont/headscale/commit/5b5298b0255098a0653da985f3b412fc133cbb40) Renamed config param for node update check internal - [`4ccff8b`](https://github.com/juanfont/headscale/commit/4ccff8bf2891d36225983ad42d0b36f28b9b368a) Added the new parameter to the integration test params ### 📊 Changes **9 files changed** (+30 additions, -5 deletions) <details> <summary>View changed files</summary> 📝 `CHANGELOG.md` (+1 -2) 📝 `config-example.yaml` (+6 -0) 📝 `config.go` (+16 -0) 📝 `integration_test/etc/alt-config.dump.gold.yaml` (+1 -0) 📝 `integration_test/etc/alt-config.yaml` (+1 -0) 📝 `integration_test/etc/config.dump.gold.yaml` (+1 -0) 📝 `integration_test/etc/config.yaml` (+1 -0) 📝 `integration_test/etc_embedded_derp/config.yaml` (+1 -0) 📝 `poll.go` (+2 -3) </details> ### 📄 Description A user with >150 machines in their tailnet reported high CPU consumption. Although for sure we have other bottlenecks, a 10 second check interval for updates might be a bit too much. This PR allows an advanced user to change this (until now hardcoded) setting. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
adam added the pull-request label 2025-12-29 02:30:35 +01:00
adam closed this issue 2025-12-29 02:30:35 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
CLI
DERP
DNS
Nix
OIDC
SSH
bug
database
documentation
duplicate
enhancement
faq
good first issue
grants
help wanted
might-come
needs design doc
needs investigation
no-stale-bot
out of scope
performance
policy 📝
pull-request
Mirrored from GitHub Pull Request
 question
regression
routes
stale
tags
tailscale-feature-gap
well described ❤️
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#1563
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?