Aks
529
Total Pages
422
Linux-Friendly Pages
107
Pages with Bias
20.2%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
301 issues found
Showing 226-250 of 301 flagged pages
Aks
Use GPUs on Azure Kubernetes Service (AKS)
...zure-aks-docs/blob/main/articles/aks/use-nvidia-gpu.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Mention
Summary
The documentation mentions Windows-specific tools (Azure PowerShell) and lists them before Linux alternatives when describing how to create an AKS cluster. However, all technical examples and instructions for GPU enablement, node pool management, and workload deployment use cross-platform tools (Azure CLI, kubectl) and Linux-based node pools. There are no PowerShell-only examples, nor are Windows node pools supported for GPU workloads.
Recommendations
- List Linux and cross-platform options before Windows-specific tools when introducing cluster creation methods.
- Clarify that GPU workloads are only supported on Linux node pools and that Windows node pools are not supported for GPU workloads.
- If mentioning Windows tools (e.g., Azure PowerShell), provide parity by linking to equivalent Linux instructions or tools.
- Consider removing or de-emphasizing Windows-specific references in sections where they are not relevant to GPU workloads.
Create Pull Request
Aks
What is Azure Kubernetes Service (AKS)?
...s/azure-aks-docs/blob/main/articles/aks/what-is-aks.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is generally cross-platform and does not provide command-line examples, but it does show some Windows bias in the following ways: Windows containers are explicitly called out as a use case, and Windows Server containers are mentioned in the features table before Linux equivalents. There is also a reference to Visual Studio Code, which, while cross-platform, is often associated with Windows development. However, there are no command-line examples or tooling instructions that are Windows-specific, and Linux is implicitly supported throughout.
Recommendations
- Add explicit mentions of Linux container support and Linux node pools alongside Windows containers in use case and feature lists.
- Ensure that examples and feature descriptions highlight Linux parity, such as referencing both Linux and Windows container workloads.
- Where development tooling is mentioned, clarify cross-platform compatibility (e.g., Visual Studio Code is available on Linux/macOS).
- Consider adding a section or note on AKS support for Linux-specific workloads and tools.
Aks
Optimize costs in Azure Kubernetes Service (AKS)
...aks-docs/blob/main/articles/aks/best-practices-cost.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Summary
The documentation is largely platform-neutral, focusing on Azure-specific features and Kubernetes concepts. However, there is a notable mention of 'Azure Hybrid Benefit for AKS', which is exclusively applicable to Windows VMs and Windows licensing. This section provides a cost optimization strategy that is only relevant for Windows workloads, without an equivalent Linux-focused benefit or alternative.
Recommendations
- Clarify that Azure Hybrid Benefit is only applicable to Windows VMs, and explicitly state that Linux VMs do not have a comparable licensing benefit.
- Consider adding a brief note or section on cost optimization strategies that are unique to Linux workloads, such as leveraging open-source licensing, or highlight that Linux VMs do not incur OS licensing costs.
- Ensure parity in examples and recommendations by mentioning both Windows and Linux where relevant, especially in sections discussing VM types, licensing, or cost-saving features.
Aks
Install existing applications with Helm in Azure Kubernetes Service (AKS)
...ure-aks-docs/blob/main/articles/aks/kubernetes-helm.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation references Windows tools (Azure PowerShell) before Linux equivalents (Azure CLI) when listing options for creating an AKS cluster, but otherwise provides platform-neutral command-line examples and guidance. No PowerShell-specific commands or Windows-only tools are used in the main workflow, and Linux is explicitly mentioned as the required node OS for Helm workloads.
Recommendations
- List Azure CLI before Azure PowerShell when suggesting ways to create an AKS cluster, as CLI is cross-platform and more commonly used on Linux/macOS.
- Explicitly state that all example commands are platform-agnostic and can be run on Linux, macOS, or Windows (with appropriate shell).
- Consider providing brief notes or links for Linux/macOS users where Azure PowerShell is mentioned, clarifying that Azure CLI is recommended for non-Windows platforms.
Aks
Kubernetes on Azure tutorial - Scale applications in Azure Kubernetes Service (AKS)
...cs/blob/main/articles/aks/tutorial-kubernetes-scale.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for scaling AKS nodes, but PowerShell (a Windows-centric tool) is given equal prominence as Azure CLI. The 'Before you begin' section lists Azure CLI first, but also includes Azure PowerShell requirements and installation instructions, which may suggest a Windows-oriented workflow. However, all core Kubernetes commands (kubectl) are platform-agnostic and examples are not Windows-specific. No explicit Windows-only tools or patterns are present, and Linux/macOS users can follow all steps using Azure CLI and kubectl.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Consider moving Azure PowerShell instructions to a separate section or appendix, or clearly label them as Windows-specific.
- Add explicit notes or links for Linux/macOS users regarding Azure CLI installation and usage.
- Ensure that CLI examples are shown before PowerShell, and that PowerShell is presented as an alternative for Windows users.
Aks
Kubernetes on Azure tutorial - Upgrade an Azure Kubernetes Service (AKS) cluster
...in/articles/aks/tutorial-kubernetes-upgrade-cluster.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides parallel instructions for Azure CLI, Azure PowerShell, and the Azure portal throughout. However, Azure PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and in some sections, PowerShell examples appear before or alongside CLI examples. There is no explicit Linux bias, but the inclusion and prominence of PowerShell may create friction for Linux/macOS users, as PowerShell is less commonly used on those platforms. No steps are Windows-only, and all CLI commands are cross-platform.
Recommendations
- Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Consider listing Azure CLI examples before PowerShell in each section to reflect usage patterns on Linux/macOS.
- Add a short note clarifying that PowerShell is optional and primarily used by Windows users.
- Where possible, provide bash shell examples for common validation or scripting tasks.
- Review and ensure that all instructions and screenshots are platform-neutral or include Linux/macOS variants if relevant.
Aks
Upgrade the Azure Kubernetes Service (AKS) cluster control plane
...cs/blob/main/articles/aks/upgrade-aks-control-plane.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and Azure portal, with PowerShell (a Windows-centric tool) given equal prominence to Azure CLI. In several sections, PowerShell examples are presented immediately after CLI, and installation instructions for Azure PowerShell are referenced alongside Azure CLI. There are no explicit Linux/macOS shell examples (e.g., Bash, zsh), nor are Linux-specific considerations or alternative tools mentioned. The CLI examples are cross-platform, but PowerShell is a Windows-first technology, and its inclusion without Linux shell alternatives may create friction for Linux/macOS users.
Recommendations
- Clarify that Azure CLI commands work natively on Linux/macOS and Windows, and highlight cross-platform compatibility.
- Consider omitting PowerShell examples or moving them after CLI and portal examples, as CLI is the primary cross-platform tool.
- Add explicit Bash/zsh shell examples where relevant, especially for scripting or automation tasks.
- Include notes or links for Linux/macOS users regarding installation and usage of Azure CLI.
- If PowerShell is included, mention that PowerShell Core is available cross-platform, but CLI is generally preferred on Linux/macOS.
Aks
Control cluster and node access using Conditional Access with AKS-managed Microsoft Entra integration
...b/main/articles/aks/access-control-managed-azure-ad.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is generally cross-platform, using Azure CLI and kubectl commands that work on both Windows and Linux/macOS. However, there is a subtle Windows bias: all portal navigation instructions use the Azure portal UI, which is more commonly used by Windows users, and there are no explicit Linux/macOS-specific instructions or examples (e.g., SSH command-line usage outside Azure CLI, or references to native SSH clients). The documentation does not mention PowerShell or Windows-only tools, but it also does not provide parity for Linux/macOS users who may use different workflows or tools.
Recommendations
- Add explicit Linux/macOS command-line examples for SSH access, such as using native ssh commands with Entra ID authentication.
- Include notes or sections on using Azure CLI and kubectl on Linux/macOS, including installation instructions or troubleshooting tips for those platforms.
- Provide parity in portal navigation instructions by referencing Azure CLI or REST API alternatives for users who prefer command-line or automated workflows.
- Clarify that all CLI commands are cross-platform and provide links to platform-specific installation guides.
Aks
Deploy an AI Model on Azure Kubernetes Service (AKS) with the AI Toolchain Operator in the Azure Portal (Preview)
...ain/articles/aks/ai-toolchain-operator-azure-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for connecting to AKS, but the PowerShell example is given equal prominence and is mentioned before Linux/macOS alternatives. There is no explicit Linux/macOS bias, but the presence of PowerShell-specific instructions and references to connecting via PowerShell locally may create friction for non-Windows users. The use of Azure Cloud Shell (which is cross-platform) helps mitigate this, but the documentation could better highlight Linux/macOS workflows.
Recommendations
- Explicitly mention that Azure CLI and kubectl commands work natively on Linux and macOS, and provide installation links for these platforms.
- Move Azure CLI instructions before PowerShell instructions to reflect the cross-platform default.
- Add a note clarifying that PowerShell is primarily for Windows users, and that Linux/macOS users should use Azure CLI.
- Provide troubleshooting tips for Linux/macOS users (e.g., permissions, path issues) when using kubectl and Azure CLI.
- Consider including screenshots or examples from Linux/macOS terminals in addition to Azure portal images.
Aks
Fine-tune and deploy an AI model on Azure Kubernetes Service (AKS) with the AI toolchain operator add-on
...b/main/articles/aks/ai-toolchain-operator-fine-tune.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page references Windows-specific tools and patterns before Linux equivalents, notably in the cluster creation step, where Azure PowerShell is mentioned alongside Azure CLI and Azure Portal. However, all command-line examples throughout the tutorial use bash syntax and kubectl, which are cross-platform and Linux-friendly. No PowerShell-specific commands or Windows-only tools are used in the main workflow, but the initial mention of PowerShell and the ordering of quickstart links may subtly prioritize Windows users.
Recommendations
- List Linux/macOS-friendly options (Azure CLI, Portal) before Windows-specific tools (PowerShell) in the 'Before you begin' section.
- Clarify that Azure CLI and kubectl commands work on Linux, macOS, and Windows (including WSL), and provide links to platform-specific installation guides.
- If referencing PowerShell, also mention Bash or Zsh for parity, or provide example commands for both where relevant.
- Consider adding a note that all steps are fully supported on Linux/macOS environments.
Aks
Integrate an MCP Server with the AI Toolchain Operator on Azure Kubernetes Service (AKS)
...cs/blob/main/articles/aks/ai-toolchain-operator-mcp.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page exhibits mild Windows bias in the prerequisites section, where Windows-centric tools (Azure PowerShell and Azure portal) are mentioned alongside Azure CLI, and Windows-specific instructions are listed before Linux equivalents. However, all actual technical steps and code samples use cross-platform tools (kubectl, curl, Python, uv), and there are no PowerShell-only commands or Windows-only patterns in the main workflow.
Recommendations
- List Azure CLI as the primary method for AKS cluster creation, with Linux/macOS instructions first, and mention PowerShell/portal as alternatives.
- Explicitly note that all commands (kubectl, curl, uv, Python) are cross-platform and provide any necessary Linux/macOS-specific notes if differences exist.
- If showing multiple ways to create AKS clusters, provide Linux/macOS shell examples before Windows/PowerShell.
- Add a short section confirming Linux/macOS compatibility for the workflow, especially for Python virtual environment setup.
Aks
Create an AKS-managed GPU node pool on Azure Kubernetes Service (AKS)
...s-docs/blob/main/articles/aks/aks-managed-gpu-nodes.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias in the 'Before you begin' section, where Windows tools (Azure PowerShell) and the Azure portal are mentioned alongside the Azure CLI as options for cluster creation, with PowerShell listed before the portal. However, all actual command-line examples throughout the page use Azure CLI, which is cross-platform and works on both Linux and Windows. There are no PowerShell-specific examples, and the main node pool creation instructions focus on Ubuntu and Azure Linux, with explicit statements that Windows node pools are not supported for this feature. There is a minor omission: no explicit Linux shell (bash) examples are shown for cluster creation, and the quickstart links include a PowerShell guide but not a bash-specific guide.
Recommendations
- List Linux-native tools (bash, shell scripts) before or alongside Windows tools when presenting options for cluster creation.
- Provide explicit bash or Linux shell examples for cluster creation, not just Azure CLI commands.
- Clarify that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
- Consider adding a Linux quickstart link (e.g., bash or shell) to match the PowerShell quickstart link.
Aks
API Server Authorized IP Ranges in Azure Kubernetes Service (AKS)
...b/main/articles/aks/api-server-authorized-ip-ranges.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows Example In Linux Section
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major operations, ensuring parity for Linux/macOS and Windows users. However, there are some signs of Windows bias: PowerShell examples are given equal prominence to CLI, and Windows-specific tools (e.g., Invoke-RestMethod) are mentioned for IP address retrieval. Additionally, in the PowerShell section, the Linux shell command for IP retrieval is shown, which may confuse users. There is also a reference to a Windows support article for finding your IP address.
Recommendations
- Clearly separate Linux/macOS and Windows instructions for IP address retrieval, using native tools for each (e.g., curl for Linux/macOS, PowerShell for Windows).
- In PowerShell sections, avoid showing bash commands; instead, provide PowerShell-native equivalents.
- When referencing external help articles, include links for both Windows and Linux/macOS users.
- Consider listing Azure CLI (cross-platform) examples before PowerShell (Windows-centric) examples.
- Explicitly state that Azure CLI works on Windows, Linux, and macOS, and provide installation links for all platforms.
Aks
Monitor Inference Metrics via the AI Toolchain Operator
.../main/articles/aks/ai-toolchain-operator-monitoring.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Mention
Summary
The documentation mentions Windows and PowerShell as options for creating an AKS cluster before Linux alternatives, and includes a link to an AKS quickstart using PowerShell. However, all command-line examples use kubectl and Azure CLI, which are cross-platform and compatible with Linux/macOS. There are no Windows-only tools or examples, and Linux users can follow all steps without issue.
Recommendations
- List Linux/CLI options before Windows/PowerShell in the 'Before you begin' section to avoid implying Windows is the default or preferred platform.
- Clarify that Azure CLI and kubectl commands work on Linux, macOS, and Windows.
- Add explicit mention or links to Linux/macOS installation guides for Azure CLI and kubectl.
- Consider removing or de-emphasizing PowerShell unless a Windows-specific workflow is required.
Aks
Configure Tool Calling with an AI Inference Service using the AI Toolchain Operator on Azure Kubernetes Service (AKS)
...ain/articles/aks/ai-toolchain-operator-tool-calling.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias in the prerequisites section, where Windows-specific tools (Azure PowerShell) are mentioned alongside Azure CLI and the Azure portal, but Linux/macOS equivalents (such as Bash scripts or Linux-specific guidance) are not explicitly referenced. The order of presentation puts Azure CLI first (cross-platform), but PowerShell is mentioned before the portal, and no Linux-specific package manager instructions are given for installing Azure CLI. No Linux/macOS-specific troubleshooting or examples are provided. All command-line examples use kubectl and curl, which are cross-platform, and the Python code is OS-agnostic.
Recommendations
- Explicitly mention that Azure CLI and kubectl commands work on Linux/macOS as well as Windows.
- Provide links or instructions for installing Azure CLI on Linux/macOS (e.g., apt, yum, Homebrew).
- Add a note that Azure PowerShell is primarily for Windows users, and suggest Bash or shell alternatives for Linux/macOS.
- Include troubleshooting steps or tips for Linux/macOS users, such as handling permissions or networking differences.
- Consider listing the Azure portal and CLI before PowerShell to avoid Windows-first ordering.
Aks
About the Availability Sets deprecation in Azure Kubernetes Services (AKS)
...ocs/blob/main/articles/aks/availability-sets-on-aks.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively uses Azure CLI and kubectl commands, which are cross-platform, but does not mention or provide any Windows-specific tools (like PowerShell) nor does it address Linux/macOS-specific nuances. However, there is a subtle bias in installation instructions: the Azure CLI installation link does not clarify Linux/macOS installation steps, and no explicit Linux/macOS shell examples or troubleshooting are provided. The examples are generic and do not show Windows or Linux shell prompts, but the lack of explicit Linux parity (such as bash-specific notes, package manager commands, or OS-specific troubleshooting) may create minor friction for non-Windows users.
Recommendations
- Add explicit instructions or links for installing Azure CLI on Linux and macOS.
- Include example shell commands with bash/zsh prompts or note that commands are cross-platform.
- Mention any OS-specific requirements or troubleshooting steps for Linux/macOS users.
- Clarify that Azure CLI and kubectl are supported on all major platforms, and provide links to platform-specific documentation.
Aks
Configure multiple ingress controllers and NGINX ingress annotations with the application routing add-on for Azure Kubernetes Service (AKS)
...b/main/articles/aks/app-routing-nginx-configuration.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation relies heavily on Azure CLI for cluster and networking operations, which is available cross-platform but is most commonly associated with Windows environments. There is no mention of Linux/macOS-specific package managers or shell environments, nor are there examples for Linux-native tools or workflows. Azure CLI commands are presented first and exclusively for all provisioning and configuration steps, with no alternative instructions for Linux users (e.g., Bash scripts, Linux-specific notes, or package installation via apt/yum/homebrew). There is no evidence of PowerShell-specific commands, but the overall workflow assumes Azure CLI usage, which is more familiar to Windows users.
Recommendations
- Explicitly state that Azure CLI is cross-platform and provide installation instructions for Linux and macOS (e.g., apt, yum, homebrew).
- Include example shell commands for Linux/macOS environments where appropriate (e.g., using Bash variables, file creation, or permissions).
- Add notes or sections for Linux/macOS users, such as differences in environment setup, file paths, or troubleshooting.
- Mention alternative tools (e.g., Azure PowerShell, REST API, Terraform) and clarify their cross-platform compatibility.
- Ensure that all command-line examples are tested and work in Bash/zsh on Linux/macOS, not just Windows CMD/PowerShell.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation provides a balanced overview of both Linux and Windows node OS upgrade channels in AKS, but there are subtle biases. Windows-specific behaviors and limitations are called out, but Linux mechanisms (like 'unattended upgrades' and 'dnf-automatic') are described in more detail. The CLI examples and operational guidance are generic and apply to both OS types, but troubleshooting and operational notes (such as reboot management) mention Windows tools (e.g., kured) without Linux equivalents. Windows limitations (e.g., lack of SecurityPatch support) are clearly stated, but Linux patterns are explained first and in more depth.
Recommendations
- Provide explicit Linux and Windows CLI examples where behaviors differ (e.g., how to check patch status on Windows nodes).
- Mention Linux and Windows operational tools in parallel (e.g., for reboot management, list both kured for Linux and Windows equivalents if available).
- Ensure that troubleshooting and FAQ sections include parity for both OS types, not just Linux.
- Add a table or section summarizing differences and similarities in upgrade mechanisms for Linux and Windows, including supported channels and patching tools.
- Where limitations are described (e.g., SecurityPatch not supported on Windows), offer guidance or alternatives for Windows users.
Aks
Certificate Rotation in Azure Kubernetes Service (AKS)
...ks-docs/blob/main/articles/aks/certificate-rotation.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation provides both Linux and Windows file paths when verifying TLS Bootstrapping, but Linux paths are mentioned first. There are no PowerShell-specific examples, and all command-line instructions use Azure CLI and Bash syntax, which are cross-platform. The only explicit Windows reference is the file path for TLS Bootstrapping, but it is presented alongside the Linux equivalent. No sections are Windows-only, and Linux users can complete all tasks without friction.
Recommendations
- Continue to provide both Linux and Windows file paths when referencing node configuration.
- If possible, add explicit PowerShell or Windows Command Prompt examples for users who prefer those environments.
- Clarify in the prerequisites that Azure CLI and Bash commands work on Windows via WSL, Azure CLI for Windows, or Git Bash.
- Ensure parity in troubleshooting steps for both Linux and Windows nodes.
Aks
Concepts - Access and identity in Azure Kubernetes Services (AKS)
...e-aks-docs/blob/main/articles/aks/concepts-identity.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation consistently references Azure CLI commands (e.g., az login, az aks get-credentials) and kubectl, which are cross-platform, but it implicitly assumes a Windows environment by omitting any mention of Linux/macOS-specific considerations, such as authentication flows, file paths, or shell differences. The sequence of commands and authentication steps are described generically, but there are no explicit Linux/macOS examples, nor is there guidance for users who may encounter platform-specific issues (e.g., browser-based authentication, credential storage locations). The documentation does not mention PowerShell, but it does not provide parity for Linux/macOS users in terms of examples or troubleshooting.
Recommendations
- Add explicit notes confirming that all CLI commands work on Linux/macOS, and mention any platform-specific prerequisites (e.g., installing Azure CLI, kubectl).
- Include example command sequences for Linux/macOS users, especially where file paths (e.g., .kube/config) or authentication flows may differ.
- Highlight any differences in browser-based authentication or credential storage on Linux/macOS.
- Provide troubleshooting tips for Linux/macOS users, such as handling CLI authentication issues or environment variable setup.
- Ensure that screenshots, if any, are not exclusively Windows-oriented.
Aks
Concepts - IP address planning in Azure Kubernetes Service (AKS)
...n/articles/aks/concepts-network-ip-address-planning.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page shows mild Windows bias by referencing Azure CLI and Azure Resource Manager templates as primary configuration methods, both of which are cross-platform but often associated with Windows environments. The Azure portal is also mentioned, which is platform-agnostic. No Linux/macOS-specific tools or shell examples (e.g., Bash) are provided, and PowerShell is not mentioned. All examples and instructions are generic and do not include OS-specific commands, but the ordering and framing may subtly prioritize Windows-centric workflows.
Recommendations
- Explicitly mention that Azure CLI is available and supported on Linux/macOS, and provide example commands in Bash syntax.
- Include references to Linux-native tools or workflows where relevant (e.g., using kubectl from a Linux shell).
- Add a note clarifying that all configuration methods (CLI, portal, templates) are cross-platform.
- If possible, provide example commands for both Bash and PowerShell to demonstrate parity.
Aks
Concepts - Storage in Azure Kubernetes Services (AKS)
...re-aks-docs/blob/main/articles/aks/concepts-storage.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Example
Missing Linux Example
Summary
The documentation provides both Linux and Windows information in some places, but there is a notable Windows bias in the persistent volume claim section, where Windows-specific mounting examples are given after the Linux example. However, the Linux example is more detailed and comes first. There is a brief mention that persistent volumes can't be shared between Windows and Linux pods, but no further guidance for Linux-specific scenarios or troubleshooting. The documentation does not provide PowerShell-heavy or Windows tools/patterns, but Windows mounting syntax is explicitly shown, while Linux mounting is implied by the path. There are no Linux/macOS-specific examples or troubleshooting tips.
Recommendations
- Add explicit Linux mounting examples (e.g., show mounting to /mnt/data, clarify Linux path conventions).
- Provide troubleshooting tips for Linux-specific issues (e.g., file system compatibility, SELinux/AppArmor).
- Include a table or section comparing Windows and Linux storage behaviors, limitations, and best practices.
- Ensure parity in example manifests for both OS types, including access modes and file system types.
- Clarify any differences in CSI driver support or configuration for Linux vs. Windows nodes.
Aks
Configure Azure CNI Pod Subnet - Dynamic IP Allocation and enhanced subnet support
...icles/aks/configure-azure-cni-dynamic-ip-allocation.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation exclusively uses Azure CLI commands and references Azure Portal for monitoring, both of which are cross-platform but have a strong association with Windows environments. There are no explicit Linux/macOS-specific instructions, nor are there any examples using Linux-native tools or shell patterns beyond basic Bash. The monitoring section references downloading a YAML file and using kubectl, which is cross-platform, but the overall workflow assumes familiarity with Azure-centric tooling, which is more common in Windows-centric environments. There are no PowerShell-specific examples, but the lack of Linux/macOS-specific troubleshooting or alternative approaches may create friction for non-Windows users.
Recommendations
- Explicitly state that Azure CLI and kubectl commands work on Linux/macOS as well as Windows.
- Provide example commands for installing Azure CLI and kubectl on Linux/macOS.
- Include troubleshooting tips for Linux/macOS environments (e.g., file permissions, shell differences).
- Mention alternative monitoring workflows for users who do not use the Azure Portal GUI.
- Clarify that all steps can be performed in Bash on Linux/macOS, and highlight any OS-specific caveats if they exist.
Aks
Limit access to kubeconfig in Azure Kubernetes Service (AKS)
...cs/blob/main/articles/aks/control-kubeconfig-access.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation references Windows and PowerShell in the 'Before you begin' section, listing Azure PowerShell and the Azure portal as options for creating an AKS cluster before mentioning the Azure CLI. However, all command-line examples throughout the page use Azure CLI and bash-style syntax, which is cross-platform and works on Linux, macOS, and Windows (with WSL or bash). There are no explicit Windows-only tools or commands, and no examples are given exclusively for PowerShell or cmd.exe. The only minor bias is the mention of PowerShell as a primary option for cluster creation, and the ordering of Windows-centric tools before Linux equivalents.
Recommendations
- List Azure CLI as the first option for cluster creation, as it is cross-platform.
- Clarify that Azure CLI commands work on Linux, macOS, and Windows (with WSL or bash).
- Provide explicit notes or links for Linux/macOS users on installing and using Azure CLI.
- If mentioning PowerShell, also mention bash or shell scripts for Linux/macOS users.
- Avoid implying PowerShell is the default or preferred method unless necessary.
Aks
Concepts - Security in Azure Kubernetes Services (AKS)
...e-aks-docs/blob/main/articles/aks/concepts-security.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation provides a balanced overview of both Linux and Windows node options in AKS, but there is a slight Windows bias in the node security section. Windows Server nodes are mentioned explicitly alongside Linux nodes, and a dedicated link is provided for adding Windows Server node pools with containerd. However, Linux options are described in greater detail, especially regarding security-optimized OS choices. The order of mention sometimes places Windows after Linux, but Windows-specific tools and patterns (such as Windows Server releases and containerd usage) are highlighted. No examples or instructions are given that are Windows-only, and Linux security features (AppArmor, seccomp, SELinux) are recommended as best practices.
Recommendations
- Ensure that any references to Windows node pools are matched with equivalent Linux instructions or links.
- If mentioning Windows-specific features (e.g., containerd on Windows Server), provide parallel details for Linux (e.g., containerd on Ubuntu/Azure Linux).
- Maintain consistent ordering (Linux and Windows) or clarify that both are supported equally.
- Add explicit Linux examples or links where Windows examples are given, to reinforce parity.