Skip to content
This repository has been archived by the owner on Jul 22, 2022. It is now read-only.

IPv6 #24

Closed
jtagcat opened this issue Aug 4, 2020 · 3 comments
Closed

IPv6 #24

jtagcat opened this issue Aug 4, 2020 · 3 comments
Labels
enhancement New feature or request

Comments

@jtagcat
Copy link
Collaborator

jtagcat commented Aug 4, 2020

'By default, a container will have an IP address assigned automatically out of the pool of available IP addresses: 10.40.0.1 - 10.47.255.254. Once a container is recreated, it may receive different IP address. A container does not change an IP address if it is restarted.' I know it's docker's fault as well, but ew.

@avkonst
Copy link
Collaborator

avkonst commented Aug 4, 2020

I think that would not be possible without the support from weavenet. And I believe they would not consider to add this feature because these are the IP addresses of the cluster's VPN maintained by weavenet. It has got enough big IP range for the largest deployments in the world :) Could you please elaborate more on the motivation for this feature?

@avkonst avkonst added the enhancement New feature or request label Aug 4, 2020
@jtagcat
Copy link
Collaborator Author

jtagcat commented Aug 4, 2020

I agree, I don't need this, the larger installations probably want something like k8s anyway.

Closing as wontfix until upstream does something.

Main reason being:

caution legacy ip only; this product does not support the current generation of the internet protocol, ipv6

@jtagcat jtagcat closed this as completed Aug 4, 2020
@avkonst
Copy link
Collaborator

avkonst commented Aug 4, 2020

Waiting for this ticket resolved: weaveworks/weave#19
After Overnode will be able to pick it up

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants