About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Bias Types:
⚠️
powershell_heavy
⚠️
windows_tools
⚠️
missing_linux_example
⚠️
windows_first
Summary:
The documentation demonstrates a strong Windows bias by exclusively using PowerShell cmdlets (e.g., Add-HcsNetRoute, Get-HcsNetRoute, Remove-HcsNetRoute) for all network configuration tasks, with no mention of Linux command-line equivalents or cross-platform alternatives. The instructions assume access to a PowerShell interface and reference Windows-specific networking concepts (such as Hyper-V virtual switches and Switch Embedded Teaming), without providing guidance for users familiar with Linux networking tools or environments. There are no Linux or kubectl-based examples for managing routes or networking, and the documentation does not address how to perform these tasks if the Kubernetes nodes were running on Linux or in a more standard Kubernetes environment.
Recommendations:
- Provide equivalent Linux command-line instructions (e.g., using ip route, nmcli, or netplan) for adding, viewing, and removing routes on Kubernetes nodes.
- Include examples using kubectl or standard Kubernetes networking resources for route management, if possible.
- Clarify whether the PowerShell cmdlets are available only on Windows-based Azure Stack Edge devices, and provide alternative instructions for Linux-based environments or for users connecting via SSH.
- When describing networking concepts (e.g., virtual switches, NIC teaming), mention Linux equivalents (e.g., Linux bridges, bonding) or clarify their applicability.
- Consider reordering or supplementing examples so that Linux and cross-platform approaches are presented alongside or before Windows/PowerShell-specific methods.
Create pull request
Flagged Code Snippets
Add-HcsNetRoute -InterfaceAlias <Port number> -DestinationPrefix <Destination IP address or IP address prefix> -NextHop <IP address of next hop> -RouteMetric <Route metric number>
Add-HcsNetRoute -InterfaceAlias "Port3" -DestinationPrefix "192.168.20.0/24" -NextHop "192.168.20.1" -RouteMetric 100
Get-HcsNetRoute -InterfaceAlias <Port number>
Remove-HcsNetRoute -InterfaceAlias <Port number> -DestinationPrefix <Destination IP or IP prefix>