-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
help request: Set upstream discovery kubernetes type not work. #7026
Comments
Are there any other error logs? This is usually the case when APISIX is unable to query a valid message from k8s. |
the log level is
log message
|
Log message shows that Kubernetes Discovery did not get "testnet/explorer-reader" endpoints value from k8s Can you provide the ServiceAccount information used by the pod where apisix is located? |
yes, i know kubernetes discovery did not get "testnet/explorer-reader" endpoints value from k8s. my understanding is that apisix is deployed in k8s. configured:
I really didn't verity sa, i try it. |
Not working. |
Did you see any other logs printed by Kubernetes Discovery,
apisix/apisix/discovery/kubernetes/init.lua Line 123 in 935e62f
|
Debug mode is turn on, but two lines not show |
Kubernetes Discovery also prints log information at other execution points in addition to the places mentioned above:
Can you help to find out if there is any related content, otherwise it is difficult to locate the cause of the problem |
I also had the same problem apisix daemonset configuration file
ServiceAccount
configmap
route
Error log generated for a single request
|
What other information do I need to provide |
|
|
Maybe you only modified the configmap, but didn't restart the apisix pod? |
I'm sure I restarted the apisix pod |
@Hyt05 Can you send QQ or WeChat to my email ( root@libssl.com ) |
Modify the ConfigMap? You just need to update the route object through Admin API or Dashboard. |
Debugging in the user environment found that, If use [ apisix-2.13.3:debian apisix-2.13.3:alpine ] image, Everything works fine with apisix-2.13.3:centos image Looks like this is a bug related to environment variables or schema @spacewander @tokers @tzssangglass TKS @Hyt05 for providing a test environment |
Strange, this behavior should be consistent even on different OS. |
I can provide an environment to reproduce the problem at any time if needed |
It may be because apisix:2.13.3-centos uses apisix 2.15.0 by mistake, I have re-pushed the image, you can try again. |
Just tested, apisix:2.13.3-centos doesn't work anymore,so should i switch to 2.15, i want to be compatible with my dashbord |
I will test kubernetes discovery in APISix 2.13.3 working in native and container |
After comparing the release version and the code pr record Kubernetes-related environment variable injection only started in version 2.15.X And U can read this issue |
Thanks to @zhixiongdu027 guidance, kubernetes discovery is running correctly with the following configuration
|
I think this detail can be recorded to the FAQ. @Hyt05 Could you help to submit a PR to add a FAQ item about this? Thanks! |
I'd love to submit a PR on this, but I'm not familiar with the whole process, is there an example or documentation to refer to |
|
i have new quesion , apisix version :2.15.0 I use the gateway namespace to deploy apisix, and use the namespace traffic to deploy business services. I need to use the service discovery method to access the business. How to do it
upstem
|
Getting more debug logs by: #7026 (comment) helps us to determine if it is the same issue. |
So far, the faults in the use of kubernetes discovery that I have found mainly include four aspects:
|
This issue has been marked as stale due to 350 days of inactivity. It will be closed in 2 weeks if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the dev@apisix.apache.org list. Thank you for your contributions. |
This issue has been closed due to lack of activity. If you think that is incorrect, or the issue requires additional review, you can revive the issue at any time. |
Description
Set upstream discovery kubernetes type not work
We installed apisix using the helm method.
When the log returns
no valid upstream node: nil
, we are not quite sure what's wrong.Why are we still unable to find upstream node with this configuration?
Environment
apisix version
): 2.13.1uname -a
): Linux apisix-86b8f89954-m9qbp 5.4.141-67.229.amzn2.x86_64 change: added doc of how to load plugin. #1 SMP Mon Aug 16 12:51:43 UTC 2021 x86_64 Linuxopenresty -V
ornginx -V
): openresty/1.19.9.1curl http://127.0.0.1:9090/v1/server_info
): 3.4.18luarocks --version
):The text was updated successfully, but these errors were encountered: