I had some trouble having this work when creating the ingress controller in the kube-system namespace, while having my application service in another one. Creating the ingress controller in a brand new namespace, having application service in antoher namespace worked. Can this be due to some network isolation ?
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
Thanks for the feedback! We are currently investigating and will update you shortly.
@arkiaconsulting when you say you had trouble getting it to work, can you share some examples? Were you seeing any errors?
Actually, I'm sorry but I didn't capture the errors... :-( The only thing that I remember is that i did get a 502 when navigating to my fqdn. And looking at the logs of the ingress controller, it was not able to find a route to a local IP.
kube version: 1.10.3
Thanks @arkiaconsulting. No worries about the logs :)
Are you still seeing issues with this?
No, the issue has gone when I deployed the ingress controller in another namespace, such as:
@arkiaconsulting got it. Thanks for clarifying :)
@iainfoulds can you take a look to see if we should update this doc?
@MicahMcKittrick-MSFT I can't replicate this behavior, I've ran through this doc a couple of times this week without issue. Can you replicate this behavior when following the doc and creating the ingress controller in the kube-system namespace?
@iainfoulds I also could no repo it the other day.
@arkiaconsulting seeing as we cannot repo the issue I am assuming there was something else that was blocking you. Did you want to try an repo the issue again so we can take a look? Else we can just close this out.
@micahmckittrick-msft sure, I’ll try to reproduce
Sorry to have disturbed... I cannot reproduce. I successfully run my application with the ingress controller deployed in the kube-system namespace. The case can be closed
Thanks, @arkiaconsulting. Glad it does appear to work correctly for you.
@MicahMcKittrick-MSFT #please-close