Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document disabling route controller for self-managed networks #761

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
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