bug: invalid apisix-admin endpoint generated when relying on apisix.adminService.name and apisix.adminService.namespace

[code-tick]

Current Behavior

When deploying ingress-controller and specifying only apisix.adminService.name and apisix.adminService.namespace the resulting endpoint created is invalid.
It points to: http://[apisix.adminService.name]+[apisix.adminService.name]+".svc:"+[apisix.adminService.port]

Expected Behavior

it's supposed to point to:
http://[apisix.adminService.name]+[apisix.adminService.name]+".svc.cluster.local:"+[apisix.adminService.port]

Error Logs

No response

Steps to Reproduce

1. install APISIX Ingress Controller using helm chart
2. set apisix.adminService.namespace

Environment

• APISIX Ingress controller version
  2.0.0-rc4
• Kubernetes cluster version
  Client Version: v1.34.0
  Kustomize Version: v5.7.1
  Server Version: v1.33.4-eks-e386d34

[bzp2010]

1. Please specify the version of the Helm chart you are using.
2. Please provide the complete Helm values for checking.
3. I don't understand why the absence of the cluster.local suffix causes an error. Domain names without this suffix are supported in Kubernetes, and the suffix itself can be set to other values by cluster administrators. We do not need to preset or assume it—it's entirely unnecessary. Everything is automatically handled based on the DNS search domain.

[AlinsRan]

.cluster.local is not universally fixed across all Kubernetes clusters; it is merely the default DNS suffix.