Re: [I] bug: Enabling discovery kubernetes services configuration doesn't list cluster existing endpoints in Dashboard Service list [apisix]
moonming closed issue #11057: bug: Enabling discovery kubernetes services configuration doesn't list cluster existing endpoints in Dashboard Service list URL: https://github.com/apache/apisix/issues/11057 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] bug: Enabling discovery kubernetes services configuration doesn't list cluster existing endpoints in Dashboard Service list [apisix]
singhajitk commented on issue #11057: URL: https://github.com/apache/apisix/issues/11057#issuecomment-2032310569 > @singhajitk, I add a interface to dump k8s data , like this. > > `curl http://127.0.0.1:9092/v1/discovery/kubernetes/dump` @hanqingwu, Thank you for looking onto this. I will upgrade and try. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] bug: Enabling discovery kubernetes services configuration doesn't list cluster existing endpoints in Dashboard Service list [apisix]
hanqingwu commented on issue #11057: URL: https://github.com/apache/apisix/issues/11057#issuecomment-2031002350 @singhajitk, I add a interface to dump k8s data , like this. `curl http://127.0.0.1:9092/v1/discovery/kubernetes/dump` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] bug: Enabling discovery kubernetes services configuration doesn't list cluster existing endpoints in Dashboard Service list [apisix]
singhajitk commented on issue #11057: URL: https://github.com/apache/apisix/issues/11057#issuecomment-2022962730 > @singhajitk , From view source code , I don not find dump_data interface in discovery kubernetes . @hanqingwu, Thank you for looking into it. @shreemaan-abhishek , will this feature get added ? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] bug: Enabling discovery kubernetes services configuration doesn't list cluster existing endpoints in Dashboard Service list [apisix]
hanqingwu commented on issue #11057: URL: https://github.com/apache/apisix/issues/11057#issuecomment-2019221617 @singhajitk , From view source code , I don not find dump_data interface in discovery kubernetes . -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] bug: Enabling discovery kubernetes services configuration doesn't list cluster existing endpoints in Dashboard Service list [apisix]
singhajitk commented on issue #11057: URL: https://github.com/apache/apisix/issues/11057#issuecomment-2018308195 > @singhajitk , I think you confuse about apisix service and Kubernetes service endpoints. The dashboard only show apisix service "A service consists of a combination of public plugin configuration and upstream target information in a route" I think maybe there is no admin api to list Kubernetes service endpoints yet . Hi @hanqingwu, As per document apisix/discovery/kubernetes (https://apisix.apache.org/docs/apisix/discovery/kubernetes/) documentation, It looks like kubernetes services should get listed. The apisix services are getting listed without providing the discovery->kubernetes configuration. @shreemaan-abhishek, Please correct me if my understanding is wrong that "kubernetes services should get listed when discovery->kubernetes configuration" is enabled ? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] bug: Enabling discovery kubernetes services configuration doesn't list cluster existing endpoints in Dashboard Service list [apisix]
hanqingwu commented on issue #11057: URL: https://github.com/apache/apisix/issues/11057#issuecomment-2017104645 @singhajitk , I think you confuse about apisix service and Kubernetes service endpoints. The dashboard only show apisix service "A service consists of a combination of public plugin configuration and upstream target information in a route" I think maybe there is no admin api to list Kubernetes service endpoints yet . -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] bug: Enabling discovery kubernetes services configuration doesn't list cluster existing endpoints in Dashboard Service list [apisix]
singhajitk commented on issue #11057: URL: https://github.com/apache/apisix/issues/11057#issuecomment-2016936471 > can you confirm if the admin api also returns an empty result? this information is key to identify if the issue is with APISIX or just the dashboard. I did curl call for the admin api and it also returns empty list. The screenshot is attached  The configurations used for apisix is as below: `# # Licensed to the Apache Software Foundation (ASF) under one or more # contributor license agreements. See the NOTICE file distributed with # this work for additional information regarding copyright ownership. # The ASF licenses this file to You under the Apache License, Version 2.0 # (the "License"); you may not use this file except in compliance with # the License. You may obtain a copy of the License at # # http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed to in writing, software # distributed under the License is distributed on an "AS IS" BASIS, # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. # See the License for the specific language governing permissions and # limitations under the License. # apisix:# universal configurations node_listen:# APISIX listening port - 9080 enable_heartbeat: true enable_admin: true enable_admin_cors: true enable_debug: true extra_lua_path: /opts/custom_plugins/?.lua; enable_dev_mode: false # Sets nginx worker_processes to 1 if set to true enable_reuseport: true # Enable nginx SO_REUSEPORT switch if set to true. enable_ipv6: true # Enable nginx IPv6 resolver enable_server_tokens: true # Whether the APISIX version number should be shown in Server header # proxy_protocol: # Proxy Protocol configuration # listen_http_port: 9181 # The port with proxy protocol for http, it differs from node_listen and admin_listen. # # This port can only receive http request with proxy protocol, but node_listen & admin_listen # # can only receive http request. If you enable proxy protocol, you must use this port to # # receive http request with proxy protocol # listen_https_port: 9182 # The port with proxy protocol for https # enable_tcp_pp: true # Enable the proxy protocol for tcp proxy, it works for stream_proxy.tcp option # enable_tcp_pp_to_upstream: true # Enables the proxy protocol to the upstream server proxy_cache: # Proxy Caching configuration cache_ttl: 10s # The default caching time if the upstream does not specify the cache time zones: # The parameters of a cache - name: disk_cache_one # The name of the cache, administrator can be specify # which cache to use by name in the admin api memory_size: 50m # The size of shared memory, it's used to store the cache index disk_size: 1G# The size of disk, it's used to store the cache data disk_path: "/tmp/disk_cache_one" # The path to store the cache data cache_levels: "1:2" # The hierarchy levels of a cache # - name: disk_cache_two #memory_size: 50m #disk_size: 1G #disk_path: "/tmp/disk_cache_two" #cache_levels: "1:2" router: http: radixtree_host_uri # radixtree_uri: match route by uri(base on radixtree) # radixtree_host_uri: match route by host + uri(base on radixtree) # radixtree_uri_with_parameter: match route by uri with parameters ssl: 'radixtree_sni'# radixtree_sni: match route by SNI(base on radixtree) proxy_mode: http stream_proxy: # TCP/UDP proxy tcp:# TCP proxy port list - 9100 udp:# UDP proxy port list - 9200 # dns_resolver: # # - 127.0.0.1 # # - 172.20.0.10 # # - 114.114.114.114 # # - 223.5.5.5 # # - 1.1.1.1 # # - 8.8.8.8 # dns_resolver_valid: 30 resolver_timeout: 5 ssl: enable: true listen: - port: 9443 enable_http2: true ssl_protocols: "TLSv1.2 TLSv1.3" ssl_ciphers: "" ssl_trusted_certificate: "/usr/local/apisix/conf/ssl/ca.crt" nginx_config:# config
Re: [I] bug: Enabling discovery kubernetes services configuration doesn't list cluster existing endpoints in Dashboard Service list [apisix]
shreemaan-abhishek commented on issue #11057: URL: https://github.com/apache/apisix/issues/11057#issuecomment-2016717540 can you confirm if the admin api also returns an empty result? this information is key to identify if the issue is with APISIX or just the dashboard. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] bug: Enabling discovery kubernetes services configuration doesn't list cluster existing endpoints in Dashboard Service list [apisix]
singhajitk commented on issue #11057: URL: https://github.com/apache/apisix/issues/11057#issuecomment-2010535042 > > Dashboard Service list > > What is Dashboard Service list? Please elaborate your problem and provide more details on reproduction steps. A set of steps containing self contained minimal configurations would be appreciated. Hi @shreemaan-abhishek, Thanks for looking into this issue. From the Dashboard Service list, I mean, in APISIX Dashboard UI, service page is not listing any of existing Kubernetes endpoints after enabling "discovery kubernetes service" configuration. I have attached screenshot below.  -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] bug: Enabling discovery kubernetes services configuration doesn't list cluster existing endpoints in Dashboard Service list [apisix]
shreemaan-abhishek commented on issue #11057: URL: https://github.com/apache/apisix/issues/11057#issuecomment-2009016239 > Dashboard Service list What is Dashboard Service list? Please elaborate your problem and provide more details on reproduction steps. A set of steps containing self contained minimal configurations would be appreciated. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
