Skip to content
This repository has been archived by the owner on May 6, 2020. It is now read-only.

Clarifiy unexpected Packet private CIDR behaviour #163

Merged
merged 3 commits into from
Feb 5, 2020
Merged
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/flatcar-linux/packet.md
Original file line number Diff line number Diff line change
Expand Up @@ -110,6 +110,10 @@ module "controller" {
# Check yours from the `IPs & Networks` tab from your Packet.net account.
# If an IP block is not allocated yet, try provisioning an instance from the console in
# that region. Packet will allocate a public IP CIDR.
# Note: the private CIDR range has been observed to change unexpectedly,
# although at the time it was an empty/dormant Packet project and there had been some networking upgrades
# be sure to manually check this value again when either reusing an older project
# Note: Packet does not guarantee this CIDR to be stable if there are no servers deployed in the project and region
node_private_cidr = "10.128.156.0/25"
}

Expand Down