-
Notifications
You must be signed in to change notification settings - Fork 143
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Resolves #462 Signed-off-by: Balazs Nadasdi <balazs@weave.works>
- Loading branch information
Showing
1 changed file
with
16 additions
and
0 deletions.
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
# Use TF-Controller with IPv6 addresses. | ||
|
||
TF-Controller uses pod IP address to communicate with the runner instance. This | ||
logic fails when the runner pod has IPv6 address instead of IPv4 as it would try | ||
to construct a hostname from the IP address. | ||
|
||
The TF-Controller has a flag to use pod subdomain resolution instead of an IP | ||
address, with that enabled the controller will use cluster subdomains and it | ||
works with IPv6 addresses as the resolution is happening on cluster level. | ||
|
||
To enable this feature, you can set `usePodSubdomainResolution` to `true` in the | ||
Helm values file: | ||
|
||
```yaml | ||
usePodSubdomainResolution: true | ||
``` |