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
Broadly speaking, I think that cbdinocluster already supports some variant of IPv6, since the containers used by the docker deployer will be assigned IPv6 addresses. We don't however currently expose a mechanism to fetch those IPv6 addresses via the connstr or ips commands. Additionally, we do not support configuring the cluster in IPv4-strict or IPv6-strict modes, which may be required for some forms of testing. I believe there are a number of places that we assume IPv4 addresses when doing the initial cluster setup as well.
The text was updated successfully, but these errors were encountered:
Broadly speaking, I think that cbdinocluster already supports some variant of IPv6, since the containers used by the docker deployer will be assigned IPv6 addresses. We don't however currently expose a mechanism to fetch those IPv6 addresses via the
connstr
orips
commands. Additionally, we do not support configuring the cluster in IPv4-strict or IPv6-strict modes, which may be required for some forms of testing. I believe there are a number of places that we assume IPv4 addresses when doing the initial cluster setup as well.The text was updated successfully, but these errors were encountered: