You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It resolves all peer instances of kraken via the headless DNS service, but if the DNS service returns at least (or only) IPv6 addresses, the entire startup errors due to it then being passed to the attachPortIfMissing here: https://github.com/uber/kraken/blob/master/lib/hostlist/config.go#L109
Filtering by IPv4 would only solve the issue if the DNS returns an IPv4 address, but in our case it does not. The only solution is then to actually support IPv6 at least in this function.
To Reproduce
Steps to reproduce the behavior:
Start up a dual-stack cluster
Run kraken
Expected behavior
Kraken to run
Environments
k8s v1.21.3
The text was updated successfully, but these errors were encountered:
Describe the bug
Currently if you are running in a dual-stack IPv4/6 cluster with emphasis on IPv6, kraken is unable to run.
The major issue resides here: https://github.com/uber/kraken/blob/master/lib/hostlist/config.go#L102
It resolves all peer instances of kraken via the headless DNS service, but if the DNS service returns at least (or only) IPv6 addresses, the entire startup errors due to it then being passed to the
attachPortIfMissing
here: https://github.com/uber/kraken/blob/master/lib/hostlist/config.go#L109Filtering by IPv4 would only solve the issue if the DNS returns an IPv4 address, but in our case it does not. The only solution is then to actually support IPv6 at least in this function.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Kraken to run
Environments
k8s v1.21.3
The text was updated successfully, but these errors were encountered: