Implement support for custom internal IP mapping via HCLOUD_INSTANCES… #696
+78
−33
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.
This update adds the ability to specify custom internal IP addresses for Hetzner Cloud and Robot Instances through the
HCLOUD_INSTANCES_INTERNAL_IP_MAP
environment variable.This is especially useful when mixing cloud servers with dedicated robot servers via vSwitch / private networks. Users will need to manage the IPs of the robot servers manually anyway, this change let users specify them as well for the InternalIp field in K8S.