Repository navigation
[feat] add support for reserved IPv4 range in NodeBalancer backend allocation - #632
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #632 +/- ##
==========================================
- Coverage 75.93% 75.17% -0.77%
==========================================
Files 18 19 +1
Lines 2813 2940 +127
==========================================
+ Hits 2136 2210 +74
- Misses 464 493 +29
- Partials 213 237 +24 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
Can you document the new feature on |
I updated the docs as requested, and now I'm working on getting the Chainsaw tests implemented and working. |
Tests implemented. |
…nfigureCloudRoutes from the chart
Summary
--nodebalancer-backend-ipv4-reserved-rangeand the matching Helm value for reserving the highest/30in a configured NodeBalancer backend subnet./30below the reserved range by reading the subnet's existing NodeBalancer assignments.Rationale
Reserving the highest
/30prevents CCM-managed NodeBalancer backend allocation from consuming an address range that must remain available for networking.Validation
go test ./cloud/linode -count=1make helm-templateGeneral
Pull Request Guidelines