Hello @rholliday ,
Thanks for your query . I just tried the same YAML file using kubectl create command and it works perfectly !
Couple of things to note for troubleshooting further:
1) Try to check the events : kubectl get events <service name> Or kubectl describe service <service Name>
eg: kubectl get events aci-helloworld
2) As it is internal Load balancer , you should see LB name as "kubernetes-internal " in the Azure Portal under node resource group (i.e. Resource group starts with name MC_)
3) Another way to troubleshoot is try to see the activity logs from Azure portal for that corresponding LB
4) Some times corresponding Service Principle might not have right authorization to VNETs/RGs
5) Or you might have hit IP address limit in your subscription.
6) Try also checking for kube-controller-manager events log section.
Additional articles to check the logs
Try to check if Service Principle got expired
Let us know if those above troubleshooting helps out in find the issue.
If the above steps resolves your issue make sure to "Accept the answer" so that it will help the community out there.