mirror of https://github.com/k3s-io/k3s
b23955e835
* Fix URL pruning when joining an etcd member Problem: Existing member clientURLs were checked if they contain the joining node's IP. In some edge cases this would prune valid URLs when the joining IP is a substring match of the only existing member's IP. Because of this, it was impossible to e.g. join 10.0.0.2 to an existing node that has an IP of 10.0.0.2X or 10.0.0.2XX: level=fatal msg="starting kubernetes: preparing server: start managed database: joining etcd cluster: etcdclient: no available endpoints" Solution: Fixed by properly parsing the URLs and comparing the IPs for equality instead of substring match. Signed-off-by: Malte Starostik <info@stellaware.de> |
||
|---|---|---|
| .. | ||
| controller.go | ||
| etcd.go | ||
| etcd_int_test.go | ||
| etcd_test.go | ||
| etcdproxy.go | ||
| s3.go | ||