Tunnelcontroller for HA: Fix ip6tnl suffix to use two last bytes #125
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.
What this PR does / why we need it:
The tunnel-controller running in the vpn-shoot pods for VPN HA must create ip6 tunnel devices with unique names for each kube-apiserver. For that purpose its IPv6 address in the bonding tunnel network is used.
By mistake, only the last byte of the address was used for naming, but the IPv6 addresses are chosen randomly in the /112 subrange, i.e. the last two bytes must be considered.
Therefore, when two kube-apiserver with the same last byte have been created, there was a clash in the tunnel device name causing deletion of still needed tunnel devices and destroying the connection to these kube-apiservers.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note: