Azure-docs: Pod disruption budgets

[jrhoward]

Does AKS support pod disruption budgets?
I upgraded from 1.9.6 to 1.10.3 and the my disruption budgets were not honoured

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 7010bd58-42b1-5c90-3253-05deed855be8
• Version Independent ID: c890efb2-cdaf-a3eb-d54f-0e7ccbd4314d
• Content: Upgrade an Azure Kubernetes Service (AKS) cluster
• Content Source: articles/aks/upgrade-cluster.md
• Service: container-service
• GitHub Login: @gabrtv
• Microsoft Alias: gamonroy

[mimckitt]

Thanks for the question! We are investigating and will update you shortly.

[mimckitt]

@neilpeterson, @iainfoulds do either of you know anything about this?

@jrhoward can you tell me a bit more? What did you see when you upgraded? Were the disruptions removed or just did not work as you had expected?

[iainfoulds]

Sorry you ran into issues, @jrhoward. I don't think there's anything specific to AKS about pod disruption budgets being disregarded during upgrade, but there's a somewhat similar issue logged regarding node labels not being retained during the cluster upgrade to 1.10.3 - https://github.com/Azure/AKS/issues/468

I'd suggest creating a new issue at https://github.com/Azure/AKS/issues/ to report this behavior and allow the engineering team to track down if it's an underlying Kubernetes cluster upgrade issue or within AKS. I'll also follow up with the product group to see if they investigate the behavior. I don't think this is intentional behavior within AKS, but if there are settings that aren't honored after a cluster upgrade, I'll update the doc accordingly.

For now, @MicahMcKittrick-MSFT #please-close

[jrhoward]

Thanks for the quick response. Looks like it was operator error. Had the PDB in the wrong namespace.