Open mkilchhofer opened 1 year ago
FYI @djsly as you raised the feature request in the linked issues. Did you find a viable workaround for this?
Action required from @Azure/aks-pm
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Is your feature request related to a problem? Please describe.
We at @swisspost miss the feature to directly connect to the AKS workers via serial console (boot diagnostics) in case of an issue. The AKS agent pool does neither enable boot diagnostics on the
Virtual machine scale set
by default nor does it support to configure it inside the Agent Pools.Describe the solution you'd like The AKS agent pool supports configuration regarding boot diagnostics
Describe alternatives you've considered
kubectl debug
https://learn.microsoft.com/en-us/azure/aks/node-accessAdditional context There were already similar issues in the past which were closed due to inativity: