Hi @David Giron ,
Thanks for reaching out to Microsoft QnA.
This seems like the AKS remediator has added this taint. Without having a look at the logs, it will be difficult for us to confirm or state a reason for this.
Have you checked the kubelet or control plane logs and were you able to find anything there? You can refer to the below links.
https://learn.microsoft.com/en-us/azure/aks/kubelet-logs
https://learn.microsoft.com/en-us/azure/aks/monitor-aks#collect-resource-logs
Edit:
I researched a bit more and checked internally. Seems that this is most likely going to be the autodrain feature with spot - Automatically repairing Azure Kubernetes Service (AKS) nodes - Azure Kubernetes Service | Microsoft Learn .
Hope this helps!
-----------------------------------
Please don't forget to and if you think the information provided was useful so that it can help others in the community looking for help on similar issues.