zjc1750514326 commented on issue #11528: URL: https://github.com/apache/apisix/issues/11528#issuecomment-2317447026
> > > @zjc1750514326 > > > Please make sure discovery/nacos is turned on in DP, not CP. > > > https://apisix.apache.org/zh/docs/apisix/3.2/deployment-modes/ > > > > > > @zhoujiexiong As far as I know, Nacos clusters only have AP and CP, right? It seems that there is no DP. Currently, I am deploying a single node in my testing environment > > @zjc1750514326 > > I'm referring to the deployment model of apisix, not nacos. > > Could you show your deployment config of your APISIX(CP)? The config is similar with the snippet listed below. > > ``` > apisix: > node_listen: 1984 > deployment: > role: data_plane > role_data_plane: > config_provider: yaml > ``` @zhoujiexiong is that config? ``` deployment: role: traditional role_traditional: config_provider: etcd admin: # Default token when use API to call for Admin API. # *NOTE*: Highly recommended to modify this value to protect APISIX's Admin API. # Disabling this configuration item means that the Admin API does not # require any authentication. admin_key: - name: admin key: edd1c9f034335f136f87ad84b625c8f1 role: admin # admin: manage all configuration data # viewer: only can view configuration data - name: viewer key: 4054f7cf07e344346cd3f287985e76a2 role: viewer enable_admin_cors: true # Admin API support CORS response headers. allow_admin: # http://nginx.org/en/docs/http/ngx_http_access_module.html#allow - 127.0.0.0/24 # If we don't set any IP list, then any IP access is allowed by default. #- "::/64" admin_listen: # use a separate port ip: 0.0.0.0 # Specific IP, if not set, the default value is `0.0.0.0`. port: 9180 # Specific port, which must be different from node_listen's port. #https_admin: true # enable HTTPS when use a separate port for Admin API. # Admin API will use conf/apisix_admin_api.crt and conf/apisix_admin_api.key as certificate. admin_api_mtls: # Depends on `admin_listen` and `https_admin`. admin_ssl_cert: "" # Path of your self-signed server side cert. admin_ssl_cert_key: "" # Path of your self-signed server side key. admin_ssl_ca_cert: "" # Path of your self-signed ca cert.The CA is used to sign all admin api callers' certificates. admin_api_version: v3 # The version of admin api, latest version is v3. etcd: host: # it's possible to define multiple etcd hosts addresses of the same etcd cluster. - "http://127.0.0.1:2379"; # multiple etcd address, if your etcd cluster enables TLS, please use https scheme, # e.g. https://127.0.0.1:2379. prefix: /apisix # configuration prefix in etcd use_grpc: false # enable the experimental configuration sync via gRPC timeout: 30 # 30 seconds. Use a much higher timeout (like an hour) if the `use_grpc` is true. #resync_delay: 5 # when sync failed and a rest is needed, resync after the configured seconds plus 50% random jitter #health_check_timeout: 10 # etcd retry the unhealthy nodes after the configured seconds startup_retry: 2 # the number of retry to etcd during the startup, default to 2 #user: root # root username for etcd #password: 5tHkHhYkjr6cQY # root password for etcd tls: # To enable etcd client certificate you need to build APISIX-Base, see # https://apisix.apache.org/docs/apisix/FAQ#how-do-i-build-the-apisix-base-environment #cert: /path/to/cert # path of certificate used by the etcd client #key: /path/to/key # path of key used by the etcd client verify: true # whether to verify the etcd endpoint certificate when setup a TLS connection to etcd, # the default value is true, e.g. the certificate will be verified strictly. #sni: # the SNI for etcd TLS requests. If missed, the host part of the URL will be used. ``` -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
