hongda
hongda
kind: Service apiVersion: v1 metadata: name: service-default-service-default-dev-8080 namespace: kong spec: type: ExternalName externalName: default-service.default-dev ports: - port: 8080 like the above config, i remove the last 2 lines
ok thanks for your reply, i guess maybe it's because some dns configurations will be different like dns stale ttl, i will check the KIC code to find if there're...
i saw the configs from admin api like routes, services, targets, upstreams are just same, for 'with ports' and 'no ports' services, so if any other insights for it?
for example, if dns_valid_ttl dns_stale_ttl dns_cache_size, these 3 configurations would be different for them? maybe needs to further investigation
i saw there is no port field for upstreams json data.
one more thing: there is no traffic, we also do not use maybe active and passive healthcheck, but there still lots of dns translation requests to coredns, what is it?
from admin api, i got the target like: {"data":[{"created_at":1754238438.816,"id":"d09638ca-0b83-52be-a68c-fcd0571b5419","tags":null,"upstream":{"id":"8c167dd3-7ffb-5b98-be0b-f25c0c02eead"},"target":"xxxxx-service.xxx.svc.cluster.local:8080","weight":100}],"next":null}%
your picture means that the target data should be the ip address?