Repository navigation
NodeFlow 2.2.0 - #22
Merged
Merged
Conversation
…ion 000057) Failover rows could carry sticky_mode from migrations 000041/000051/000052 that the v2.1.0 renderer ignored. Reset it to '' so the rendered config stays byte-identical; golden files captured from gh/main (v2.1.0). Co-authored-by: Artem Ishmukhamedov <105602239+fesevu@users.noreply.github.com>
…h source Absent sticky_mode on a failover route no longer infers source from a DNS pool (balance_algorithm was silently ignored) and keeps the legacy empty value. leastping is rejected for failover regardless of stickiness. Co-authored-by: Artem Ishmukhamedov <105602239+fesevu@users.noreply.github.com>
…p stickiness note Co-authored-by: Artem Ishmukhamedov <105602239+fesevu@users.noreply.github.com>
…templates - audit: route.copy (source route, node_ids) and route_template.create/ update/delete/apply with the template id - copy results surface the manual-HAProxy-mode message - an unnamed copy on the source node gets the suffix ' (копия)' - template config carries schema_version=1; newer schemas are refused (400) - 000056 down migration uses DROP TABLE IF EXISTS Co-authored-by: Artem Ishmukhamedov <105602239+fesevu@users.noreply.github.com>
Split the route menu entry into «Копировать на ноды» and «Сохранить как шаблон», each a separate dialog with the panel dialog chrome (nf-dialog), labels above fields and right-aligned Отмена + primary footer. One muted note line; the listener hint only when a target node differs. Template description is an optional 2-row field. The library dialog lists templates as a bordered list with a per-row action menu and a confirm dialog for deletion; the route editor reuses the same save dialog. Co-authored-by: Artem Ishmukhamedov <105602239+fesevu@users.noreply.github.com>
Co-authored-by: Artem Ishmukhamedov <105602239+fesevu@users.noreply.github.com>
This was referenced Oct 15, 2026
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.
NodeFlow 2.2.0
Panel 2.2.0 · Node Agent 2.2.0 · HAProxy renderer v21
Закрепление клиентов в DNS-пулах с резервными серверами, копирование маршрутов между нодами и библиотека шаблонов. Две миграции (000056, 000057). Agent не менялся. Спасибо @fesevu (#19, #20).
Новое
leastconnв пулах с резервными серверами (Закрепление клиентов и leastconn для DNS-пулов с резервом #19). Для DNS-пула с резервным (backup) сервером теперь доступны закрепление клиентов (sticky) и распределениеleastconn. Новый failover-маршрут по умолчанию создаётся без закрепления.leastping/leastconnс допуском (tolerance) больше 0 отклоняются;leastpingвместе с закреплением поsourceтоже отклоняется.schema_version. Миграция 000056 (route_templates).Исправления
source_table: такие маршруты один раз публикуются заново с идентичным конфигом HAProxy. Повторное сохранение старого failover-маршрута в UI тоже сохраняет его распределение.route.copy) и действия с шаблонами (route_template.*) пишутся в журнал аудита.Обновление с 2.1.0
Panel. Повторно запустите установщик:
curl -fsSL https://raw.githubusercontent.com/NodeFlow-dev/nodeflow/main/install.sh | sudo shВручную: в
/opt/nodeflow/.envукажитеNODEFLOW_VERSION=2.2.0и выполнитеdocker compose pull && docker compose up -d. Миграции 000056 и 000057 применяет сам образ.Node Agent — необязательно. Код Agent в 2.2.0 не менялся, всё работает с Agent 2.1.x. Для единообразия версий: «Настройки → Node Agent» → «Обновить до 2.2.0».
Обновляетесь с 1.0.x — сначала прочитайте заметки к релизу 2.0.0: там однократный drop-in systemd для pipe-буферов ядра.
Файлы релиза
NodeFlow-Panel-2.2.0-Agent-2.2.0-install-kit.tar.gz— install kit.nodeflow-node-agent-2.2.0-linux-amd64,nodeflow-node-agent-2.2.0-linux-arm64— бинарники Node Agent.Panel поставляется образом
ghcr.io/nodeflow-dev/nodeflow-panel:2.2.0(linux/amd64 и linux/arm64). SHA-256 каждого файла — полеdigestв API релиза;install.shиinstall-node.shсверяют его сами.Включает #19 и #20 (@fesevu) с исправлениями по ревью.