feat(load-balancer): attach load balancer to specific subnetwork #1031
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lukasmetzner
had a problem deploying
to
e2e-robot
GitHub Actions
Failure
lukasmetzner
changed the title
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1031 +/- ##
==========================================
+ Coverage 66.94% 67.52% +0.58%
==========================================
Files 23 23
Lines 3237 3249 +12
==========================================
+ Hits 2167 2194 +27
+ Misses 901 885 -16
- Partials 169 170 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
lukasmetzner
changed the title
jooola
reviewed
Sep 24, 2025
lukasmetzner
temporarily deployed
to
e2e-robot
GitHub Actions
Inactive
lukasmetzner
temporarily deployed
to
e2e-robot
GitHub Actions
Inactive
This PR adds a new annotation `load-balancer.hetzner.cloud/network-ip-range`. With this annotation a user can control to which subnetwork a Load Balancer should be attached to. The value must be in the CIDR notation.
lukasmetzner
force-pushed
the
feat-load-balancer-attach-to-subnet
branch
from
c8565b8 to
0091276
Compare
lukasmetzner
temporarily deployed
to
e2e-robot
GitHub Actions
Inactive
jooola
approved these changes
Sep 26, 2025
jooola
reviewed
Sep 26, 2025
lukasmetzner
temporarily deployed
to
e2e-robot
GitHub Actions
Inactive
Contributor
Author
|
I have added a small section to our Private Networks Load Balancers guide. |
lukasmetzner
temporarily deployed
to
e2e-robot
GitHub Actions
Inactive
jooola
approved these changes
Oct 1, 2025
lukasmetzner
pushed a commit
that referenced
this pull request
Dec 15, 2025
…ation (#1052) This PR introduces additional environment variables for load balancer configuration. These variables are designed to be set globally as defaults and can be overridden using annotations. The main motivation is to improve support for GatewayAPI, as the `Gateway` annotation limit of 8 is restrictive and many settings are commonly needed across all load balancers from the same or even differen GatewayAPI providers. Additionally, this change allows environment-specific presets such as the new [subnet IP range](#1031) to be set globally. This removes the need to configure these settings in each service or use templating/patching to use the same service manifest for different environments. New environment vars: - `HCLOUD_LOAD_BALANCERS_ALGORITHM_TYPE` - `HCLOUD_LOAD_BALANCERS_DISABLE_PUBLIC_NETWORK` - `HCLOUD_LOAD_BALANCERS_HEALTH_CHECK_INTERVAL` - `HCLOUD_LOAD_BALANCERS_HEALTH_CHECK_RETRIES` - `HCLOUD_LOAD_BALANCERS_HEALTH_CHECK_TIMEOUT` - `HCLOUD_LOAD_BALANCERS_PRIVATE_SUBNET_IP_RANGE` - `HCLOUD_LOAD_BALANCERS_TYPE` - `HCLOUD_LOAD_BALANCERS_USES_PROXYPROTOCOL`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR adds a new annotation. This allows users to control which subnetwork a Load Balancer should be attached to. The value must be in the CIDR notation.