[Question] AKS created using a custom VNET without a route table is failing when trying to reach a service located in a different namespace.

[acano-arrive]

Describe scenario
I have an AKS configured using a custom vnet with 3 subnets:

Admin subnet is used for admin nodepool
App subnet is used for applications nodepool

1. publica - 10.1.16.0/20
2. admin - 10.1.32.0/20
3. app - 10.1.0.0/20

NSG: Default ports
Route table: No exist

Question
Within the same namespace, calls to {servicename} should work. For a call across namespaces, calls to {servicename}.{namespace} should work. For all calls, the fully qualified domain name {servicename}.{namespace}.svc.cluster.local should work.

Currently, only the FQDN seems to be working.

/home/app # nslookup team-service.team-dev.svc.cluster.local
Server: 10.201.0.10
Address: 10.201.0.10:53

Name: team-service.team-dev.svc.cluster.local
Address: 10.201.0.129

/home/app # nslookup team-service.team-dev
Server: 10.201.0.10
Address: 10.201.0.10:53

** server can't find location-service.tso-dev: NXDOMAIN

** server can't find location-service.tso-dev: NXDOMAIN

Not sure how can I fix this.

[microsoft-github-policy-service]

This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.

[microsoft-github-policy-service]

This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.

[microsoft-github-policy-service]

This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.

[microsoft-github-policy-service]

Action required from @Azure/aks-pm

[microsoft-github-policy-service]

Action required from @chasewilson.

[microsoft-github-policy-service]

This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.

[microsoft-github-policy-service]

This issue will now be closed because it hasn't had any activity for 7 days after stale. acano-arrive feel free to comment again on the next 7 days to reopen or open a new issue after that time if you still have a question/issue or suggestion.