Azure AKS is pretty terrible TBH in comparison to GKE.
Also lack of SLA / shady SLA does not help.
Ps. Talking as someone with hands on experience.
Ps2. Azure support is terrible and their response times are constantly breaking SLA..
Also lack of SLA / shady SLA does not help.
Ps. Talking as someone with hands on experience.
Ps2. Azure support is terrible and their response times are constantly breaking SLA..
Honestly, I've been pleasantly surprised.
The best support I got a mispleasure to work with didn’t even know how the service Im having an issue is even working... And it was a “technical” ticket.
Seems like after the last round of pouching of best support engineers by AWS, Azure is left with only outsourced mob.
Another - constant disconnections of PV..
Another - 1/3 times the new provisioned node in vmss has a broken kubelet and doesn’t successfully register in control-plane. I was literally shocked when it happened twice in a single day. Response from support was that we are supposed to monitor that ourselves and drain unsuccessfully provisioned node - (we already were and it was mentioned in opening ticket) makes scaling horizontally REALLY PAINFUL..
CNI default reservation of IPs (30) - cannot be less - so if you have a service node running and you want only few pods to run on it for HA - well sucks to be you.
Kubenet not working until up recently with anything - for example AG, tho AG is a disaster of a service by itself.
Various API failures related to networking - sometimes control-plane lost connection to AKS subnet for some time (fixed by itself by still...)