# Welcome to the Azure Kubernetes Service enabled by Azure Arc (AKS Arc) repo This is where the AKS Arc team will track features and issues with AKS Arc. We will monitor this repo in order to engage with our community and discuss questions, customer scenarios, or feature requests. Checkout our projects tab to see the roadmap for AKS Arc!
MIT License
111
stars
45
forks
source link
[BUG] Mixed OS cluster - using NoSchedule taints affects Windows Nodes Exporter Daemonset #235
Describe the bug
By setting a noschedule taint at Windows node pools with -taints node.kubernetes.io/os=Windows:NoSchedule no metrics from Windows nodes are available because the node exporter DaemonSet doesn't get deployed.
Describe the bug By setting a noschedule taint at Windows node pools with
-taints node.kubernetes.io/os=Windows:NoScheduleno metrics from Windows nodes are available because the node exporter DaemonSet doesn't get deployed.To Reproduce Create a node pool with
-taints node.kubernetes.io/os=Windows:NoSchedulelike described here: mixed-OS Kubernetes clusters using node selectors or taints and tolerations and check the monitoring data as described here:Monitor and logging data on Azure Kubernetes Service on Azure Stack HCI and Windows Server
Expected behavior The Windows node exporter should tolerate noschedule taints.
Screenshots A cluster without noschedule taints:
A cluster with noschedule taints at Windows nodepools
Environment (please complete the following information):
Additional context
Collect log files