-
Notifications
You must be signed in to change notification settings - Fork 516
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
Etcd advertisedSubnets #7947
Comments
Yes, probably advertised subnets might come from a more broad range of addresses. Looking for external IP as advertised? It might help if you could describe a scenario. |
Use case - multi cloud setup without kubespan/ipsec/etc (direct connection). To make p2p connections between etcd, we need to advertise the external (public) IP, which not exist on the node. PS. I did not notice any error messages when Talos did not find the advertised IP too. Probably we need to add error messages at boot time too. Thanks. |
Fixes siderolabs#7947 This way etcd advertisted address can be picked from the `external IPs` of the machine. Signed-off-by: Andrey Smirnov <[email protected]>
Fixes siderolabs#7947 This way etcd advertised address can be picked from the `external IPs` of the machine. Signed-off-by: Andrey Smirnov <[email protected]>
Bug Report
Description
Etcd advertisedSubnets is the network (filtered ip) which can not exist on the node.
But we use
talos/internal/app/machined/pkg/controllers/etcd/spec.go
Line 97 in e9c7ac1
Probably we need to use at least nodeIP+platformIP (dnat-ip).
Or check if advertisedSubnets is a single IP use it as is?
What do you think?
Thanks.
Environment
The text was updated successfully, but these errors were encountered: