[BUG] Install-AksHci on Windows Server fails waiting for flux-logs-agent
- Dominant language
- PowerShell
- Stars
- 118
- Forks
- 63
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug**
Deployment of the AKS Management Cluster on Windows Server stops on ‘waiting for flux-logs-agent’ until timeout.
**To Reproduce**
Steps to reproduce the behavior:
https://learn.microsoft.com/en-us/azure/aks-hybrid-edge/windows-server/kubernetes-walkthrough-powershell
Witnessed on multiple versions multiple platforms.
**Expected behavior**
Before we noticed this issue, the last successful deployment was in june.
The output and logs collected are from release 1.3.0.10605 on a lab server. Logs from Get-AksHciLogs are available.
Tested Windows OS-es
- Windows Server 2022
- Windows Server 2025
Issue description:
Deploying the management cluster no longer succeeds for AKSHCI on Windows server.
The deployment (install-akshci) gets stuck waiting until timeout at:
We think the azure-arc-k8sagents chart does not finish its deployment or no longer contains the components checked by the powershell module.
We’ve witnessed this first on agent 1.36.1 which stopped at waiting for metrics-agent. On 1.37.3 this changed to flux-agent-logs
Running pods:
deployments
Get events -n azure-arc after 5 minutes of waiting for flux-logs-agent
Contributor guide
Research direction
Start with the Windows Server Kubernetes walkthrough and the Install-AksHci deployment logs collected by Get-AksHciLogs for release 1.3.0.10605. Compare the azure-arc deployment state and wait condition across the reported agent versions; done means the management cluster installs without timing out on the listed Windows Server versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, kubernetes, powershell
- Domain
- cloud, devops, infrastructure, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100