3 ms·

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. Azur

by pojzon 7y ago

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..

GordonS 7y ago
Counterpoint to your PS2 - I've used Azure support at both my enterprise job and my microISV - each time the responses have been quite quick, and each time they have been helpful. Honestly, I've been pleasantly surprised.
- pojzon 7y ago
  First response is often generated by automat. A generic one “hello this is X ill take care of your case” and the next real person response can happen the very next day when the ticket urgency is CRITICAL. Thats hilarious. 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.
nfg 7y ago
I’m keen to hear what problems you’ve had with AKS if you’ve got time to share them here.
- pojzon 7y ago
  For example - metrics-server provided by AKS from the go is running in highly insecure manner. If you want to change that -> you cannot because they have automatic tools to keep bugging you out. 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...)

by pojzon 7y ago

GordonS 7y ago

Counterpoint to your PS2 - I've used Azure support at both my enterprise job and my microISV - each time the responses have been quite quick, and each time they have been helpful. Honestly, I've been pleasantly surprised.

pojzon 7y ago
First response is often generated by automat. A generic one “hello this is X ill take care of your case” and the next real person response can happen the very next day when the ticket urgency is CRITICAL. Thats hilarious. 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.

nfg 7y ago

I’m keen to hear what problems you’ve had with AKS if you’ve got time to share them here.

pojzon 7y ago
For example - metrics-server provided by AKS from the go is running in highly insecure manner. If you want to change that -> you cannot because they have automatic tools to keep bugging you out. 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...)