|
|
|
|
|
by yebyen
2610 days ago
|
|
I will say that once in my whole time using AKS, the nginx-ingress addon failed me in a way that caused my cluster to stop serving traffic. I contacted my friend at Azure (my cluster is not high-stakes production) and learned that they were aware of the issue and had engineers already on the case. I figured it out on my own before the Azure team resolved the issue globally, there were some versions out of sync. And when I applied the fix to my own cluster, the ingress addon... put it back, breaking my traffic serving again. The fix would have been to install nginx-ingress manually and point my DNS at the LB belonging to my manually configured ingress. I just waited for them to get it solved instead. Meanwhile my cluster was not serving ingresses. That may (hopefully) never happen again, but the moral of the story is, one good reason to configure ingress yourself is that when it breaks, you can also fix it for yourself. |
|