prole/installer-config-persistence.md at main - prole - Gitea: Git with a cup of tea

chrisfu/prole

mirror of https://github.com/dredx/prole.git synced 2026-09-23 10:13:58 +00:00

chrisfu d02aadae89 Add node management workflow and installer config persistence updates

- add tools/manage-node.sh for k3s node add/remove automation with inventory reconciliation

- include kubectl drain flag compatibility and --ssh-host targeting for uninstall workflows

- persist installer cfg/env values and update deploy/database/cfg UI handling

- refresh related inventory/network artifacts and expand installer/database test coverage

Co-authored-by: Junie <junie@jetbrains.com>

2026-03-29 11:22:33 -07:00

890 B

Raw Permalink Blame History

Installer-managed configuration scope

The installer persists only explicit operator inputs and explicit connection handoff values.
For service/k3s-hosts workflows, values like PROLE_K3S_SERVER and other explicit user-entered settings are saved.
Generated local/dev endpoint mappings, generated service hostnames, and placeholder-derived values are not persisted as installer-owned facts.

Live service endpoints

Live k3s service endpoints are not installer-managed configuration.
Endpoint host/port discovery for running services is performed against the live cluster rather than persisted as static installer defaults.

Downstream behavior

Later Ansible phases are expected to discover current service endpoints from the running cluster.
Installer replay/config files remain focused on explicit intent and handoff values instead of dynamic runtime topology.