Inability to Taint Nodes in Default Node Pool in AKS

[FakeCode]

Description:

Upon configuring an AKS (Azure Kubernetes Service) cluster using Terraform, an error occurs during the deployment process. The error message states that the AKS API no longer supports the capability to apply taints to all nodes within the default node pool. Consequently, it is no longer feasible to configure this feature.

This issue is for a: (mark with an x)

• bug report -> please search issues before submitting
• feature request
• documentation issue or request
• regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Attempt to configure an AKS (Azure Kubernetes Service) cluster using Terraform, specifying node taints for the default node pool.

Any log messages given by the failure

Error: expanding default_node_pool: The AKS API has removed support for tainting all nodes in the default node pool and it is no longer possible to configure this. To taint a node pool, create a separate one.

with module.aks_cluster.azurerm_kubernetes_cluster.aks_cluster,
on modules/aks/main.tf line 15, in resource "azurerm_kubernetes_cluster" "aks_cluster":
15: resource "azurerm_kubernetes_cluster" "aks_cluster" {

Expected/desired behavior

The AKS cluster should be successfully provisioned with the specified node taints in the default node pool.

OS and Version?

macOS
Terraform - 1.7.5
vscode

Impact:

This issue impedes the configuration process of AKS clusters using Terraform, especially in scenarios where node tainting is essential for specific use cases such as workload isolation or node affinity.
The inability to apply taints to the default node pool may lead to complications in managing and organizing workloads within the AKS cluster effectively.

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Any log messages given by the failure

Expected/desired behavior

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

Versions

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.