Skip to content

Commit

Permalink
Document disabling routes for self-managed networks
Browse files Browse the repository at this point in the history
Fixes #758
  • Loading branch information
jtackaberry committed Oct 21, 2024
1 parent 9a6cfbb commit 5265309
Showing 1 changed file with 6 additions and 3 deletions.
9 changes: 6 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -142,9 +142,10 @@ If you want to use the Hetzner Cloud `Networks` Feature, head over to
the [Deployment with Networks support
documentation](./docs/deploy_with_networks.md).

If you manage the network yourself it might still be required to let the CCM know about private networks. You can do
this by adding the environment variable
with the network name/ID in the CCM deployment.
If you manage the network yourself it might still be required to let the CCM know about private networks. For example,
even with a self-managed network, it's still possible to enable private network attachment of CCM-provisioned Load
Balancers by setting the `load-balancer.hetzner.cloud/use-private-ip` annotation to `true` on the Kubernetes Service.
This functionality requires setting the following environment variables in the CCM deployment:

```
env:
Expand All @@ -153,6 +154,8 @@ with the network name/ID in the CCM deployment.
secretKeyRef:
name: hcloud
key: network
- name: HCLOUD_NETWORK_ROUTES_ENABLED
value: "false"
```

You also need to add the network name/ID to the
Expand Down

0 comments on commit 5265309

Please sign in to comment.