Forwarding this bug to docs team. Additional info:
In case user gets error like this:
New IP ranges for network 'public'(2) do not cover already allocated IPs.
User should check new network ranges and either adjust them to cover all allocated IPs, or reset the env and then update network ranges. In order to check allocated IPs user can login to any node and check IPs in /etc/astute.yaml ('network_metadata[nodes]' list). If only few nodes do not fit into new network ranges, then it's possible to delete them from environment, update network ranges, and re-add deleted nodes back.
Forwarding this bug to docs team. Additional info:
In case user gets error like this:
New IP ranges for network 'public'(2) do not cover already allocated IPs.
User should check new network ranges and either adjust them to cover all allocated IPs, or reset the env and then update network ranges. In order to check allocated IPs user can login to any node and check IPs in /etc/astute.yaml ('network_ metadata[ nodes]' list). If only few nodes do not fit into new network ranges, then it's possible to delete them from environment, update network ranges, and re-add deleted nodes back.