Skip to content
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

request help: apisix doesn't support etcd ipv6 endpoints #7100

Closed
zhendongcmss opened this issue May 22, 2022 · 10 comments · Fixed by #8245
Closed

request help: apisix doesn't support etcd ipv6 endpoints #7100

zhendongcmss opened this issue May 22, 2022 · 10 comments · Fixed by #8245
Assignees

Comments

@zhendongcmss
Copy link
Contributor

Current Behavior

image

image

Expected Behavior

No response

Error Logs

No response

Steps to Reproduce

  1. config ipv6 address in config-default.yaml

Environment

  • APISIX version (run apisix version): 2.7
  • Operating system (run uname -a):
  • OpenResty / Nginx version (run openresty -V or nginx -V):
  • etcd version, if relevant (run curl http://127.0.0.1:9090/v1/server_info):
  • APISIX Dashboard version, if relevant:
  • Plugin runner version, for issues related to plugin runners:
  • LuaRocks version, for installation issues (run luarocks --version):
@zhendongcmss zhendongcmss changed the title bug: apisix doesn't support ipv6 bug: apisix doesn't support etcd ipv6 endpoints May 22, 2022
@juzhiyuan juzhiyuan added the checking check first if this issue occurred label May 23, 2022
@juzhiyuan juzhiyuan assigned juzhiyuan and tzssangglass and unassigned juzhiyuan May 23, 2022
@zhendongcmss
Copy link
Contributor Author

The 2.10.1 has this bug too.

@zhendongcmss
Copy link
Contributor Author

image

@tzssangglass tzssangglass changed the title bug: apisix doesn't support etcd ipv6 endpoints request help: apisix doesn't support etcd ipv6 endpoints May 23, 2022
@tzssangglass
Copy link
Member

We don't indicate support for etcd ipv6 configuration in the documentation, so I don't think it's a bug. lua-resty-etcd probably needs some development if it's to be supported.

@zhendongcmss
Copy link
Contributor Author

Do you have plan to support it ? because it is urgent and important for us.

@tokers
Copy link
Contributor

tokers commented May 23, 2022

Do you have plan to support it ? because it is urgent and important for us.

Welcome to contribute this feature.

@zhendongcmss
Copy link
Contributor Author

update: lunarmodules/luasocket#381

@zhendongcmss
Copy link
Contributor Author

I use the latest luasocket SDK, apisix can connect to etcd , but it print the error when it started. I am investigating.

image

@zhendongcmss
Copy link
Contributor Author

Although it print error logs, getting and setting routes work.

@tzssangglass
Copy link
Member

It looks like the etcd health check feature is not working properly with ipv6.

@stubbornTanzhe
Copy link

pay close attention to this issue.
with my env, apisix deploy yaml and etcd yaml config by ipv6 address:

spec:
  ipFamilyPolicy: SingleStack
  ipFamilies:
  - IPv6

and my apisix pod logs:

Warning! Request etcd endpoint 'http://etcd-0.etcd-headless.apisix.svc.cluster.local:2379/version' error, host or service not provided, or not known, retry time=1
request etcd endpoint 'http://etcd-0.etcd-headless.apisix.svc.cluster.local:2379/version' error, host or service not provided, or not known
request etcd endpoint 'http://etcd-1.etcd-headless.apisix.svc.cluster.local:2379/version' error, host or service not provided, or not known
request etcd endpoint 'http://etcd-2.etcd-headless.apisix.svc.cluster.local:2379/version' error, host or service not provided, or not known

which curl etcd is success:

curl http://etcd-0.etcd-headless.apisix.svc.cluster.local:2379/version
{"etcdserver":"3.5.4","etcdcluster":"3.5.0"}
curl http://etcd-1.etcd-headless.apisix.svc.cluster.local:2379/version
{"etcdserver":"3.5.4","etcdcluster":"3.5.0"}
curl http://etcd-2.etcd-headless.apisix.svc.cluster.local:2379/version
{"etcdserver":"3.5.4","etcdcluster":"3.5.0"}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants