# 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
113
stars
45
forks
source link
[BUG] Azure ARC logcollector is missing nodeSelector os = linux #353
Describe the bug
When the Azure ARC connection is enabled it installs a deployment logcollector within namespace azure-arc.
The deployment seems to be a linux application and is unable to run on Windows kubernetes nodes.
However the deployment is missing a nodeSelector os = linux and therefore might get scheduled on Windows nodes.
Here it fails with:
Failed to pull image "mcr.microsoft.com/azurearck8s/fluent-bit-collector:1.13.1": rpc error: code = NotFound desc = failed to pull and unpack image "mcr.microsoft.com/azurearck8s/fluent-bit-collector:1.13.1": no match for platform in manifest: not found
To Reproduce
Steps to reproduce the behavior:
Install new Hybrid AKS cluster with Azure ARC enabled
Describe the bug When the Azure ARC connection is enabled it installs a deployment
logcollector
within namespaceazure-arc
. The deployment seems to be a linux application and is unable to run on Windows kubernetes nodes. However the deployment is missing a nodeSelector os = linux and therefore might get scheduled on Windows nodes. Here it fails with:To Reproduce Steps to reproduce the behavior:
Expected behavior The deployment must be changed and a nodeSelector for linux must be added. See https://samcogan.com/kubernetes-pod-allocation-in-a-multi-os-cluster/
Environment (please complete the following information):