WIP: add rpc_public_addr_subnet config option #817
No reviewers
Labels
No Label
AdminAPI
Bug
Check AWS
CI
Correctness
Critical
Documentation
Ideas
Improvement
Low priority
Newcomer
Performance
S3 Compatibility
Testing
Usability
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#817
Loading…
Reference in New Issue
No description provided.
Delete Branch "flokli/garage:rpc_public_addr_subnet"
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?
In case
rpc_public_addr
is not set, but autodiscovery is used, thisallows filtering the list of automatically discovered IPs to a specific
subnet.
For example, if nodes should pick their IP inside a specific subnet,
but you don't want to explicitly write the IP down (as it's dynamic, or
you want to share configs across nodes), you can use this option.
Fixes #811.
add rpc_public_addr_subnet config optionto WIP: add rpc_public_addr_subnet config option@ -55,6 +55,7 @@ hexdump = "0.1"
hmac = "0.12"
idna = "0.5"
itertools = "0.12"
ipnet = "2.9.0"
This was already in the list of dependencies (through
reqwest
), but we now explicitly depend on it, too.79729da4af
to3dc836afcb