Aks
535
Total Pages
430
Linux-Friendly Pages
105
Pages with Bias
19.6%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
365 issues found
Showing 351-365 of 365 flagged pages
Aks
Security bulletins for Azure Kubernetes Service (AKS)
.../blob/main/articles/aks/security-bulletins/overview.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation includes several bulletins that are Windows-specific (e.g., WinSock, Windows Storage, NTLM hash disclosure), with detailed versioning and upgrade instructions for Windows node images. However, equivalent Linux-specific issues are also covered, and Linux node image upgrade instructions are present. There is a slight tendency to provide more granular versioning and upgrade guidance for Windows, and Windows issues are sometimes grouped together, but Linux is not omitted. No PowerShell-heavy examples or missing Linux examples are present, and the documentation does not default to Windows tools or patterns for general AKS operations.
Recommendations
- Ensure that Linux and Windows node image upgrade instructions are equally detailed and accessible, possibly by providing parallel upgrade guidance sections for both OS types.
- When listing affected versions or upgrade paths, present Linux and Windows information in parallel to avoid the perception of prioritizing one platform.
- If providing troubleshooting steps or commands, always include both Linux and Windows variants where applicable.
- Consider a summary table or matrix showing both Linux and Windows vulnerabilities and resolutions for quick cross-platform reference.
Create Pull Request
Aks
Start and stop a node pool on Azure Kubernetes Service (AKS)
...ks-docs/blob/main/articles/aks/start-stop-nodepools.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation references Windows-specific tools (Azure PowerShell) alongside cross-platform options (Azure CLI, Azure portal) when instructing users how to create an AKS cluster. Azure PowerShell is a Windows-centric tool, and its mention before Linux/macOS equivalents (Azure CLI and portal) may signal a Windows-first bias. However, the actual node pool management examples use Azure CLI, which is cross-platform, and no PowerShell-exclusive examples are provided.
Recommendations
- List cross-platform tools (Azure CLI, Azure portal) before Windows-specific tools (Azure PowerShell) when presenting options.
- Clarify that Azure CLI and Azure portal are fully supported on Linux/macOS, and provide links or notes about installation on those platforms.
- If mentioning Azure PowerShell, also mention Linux-compatible alternatives (e.g., PowerShell Core) or clarify platform compatibility.
- Consider removing or de-emphasizing Windows-specific tools unless there is unique functionality not available elsewhere.
Aks
Kubernetes on Azure tutorial - Use PaaS services with an Azure Kubernetes Service (AKS) cluster
...main/articles/aks/tutorial-kubernetes-paas-services.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for all major steps, ensuring cross-platform support. However, PowerShell examples (which are Windows-centric) are given equal prominence to Azure CLI, and in some sections (such as environment variable setup), PowerShell is presented immediately after CLI, rather than relegated to an appendix or alternative section. There are no Linux-specific examples, nor is Bash scripting shown, but the Azure CLI instructions are fully compatible with Linux/macOS. No Windows-only tools or patterns are used, and no critical steps are exclusive to Windows.
Recommendations
- Make Azure CLI the default or primary example, as it is cross-platform, and move PowerShell instructions to a secondary section or appendix.
- Explicitly mention that Azure CLI commands work on Linux/macOS and Windows, while PowerShell is primarily for Windows users.
- Add Bash scripting examples for environment variable setup to further improve Linux parity.
- Clarify in the prerequisites that PowerShell is optional and not required for Linux/macOS users.
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 to Azure CLI, and is presented in a dedicated tab. There are no Linux-specific shell examples or explicit mention of Linux/macOS environments, and PowerShell is referenced before any Linux alternatives. However, the core scaling tasks can be completed using Azure CLI, which is cross-platform.
Recommendations
- Clarify that Azure CLI is cross-platform and can be used on Linux/macOS as well as Windows.
- Consider listing Azure CLI instructions before PowerShell, or making CLI the default example.
- Explicitly mention Linux/macOS compatibility in the prerequisites and examples.
- Add a note that PowerShell examples are primarily for Windows users, and that Linux/macOS users should use Azure CLI.
- Provide bash shell examples for common kubectl commands where appropriate.
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
Windows First
Powershell Heavy
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and Azure portal, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is always presented as a primary option. There are no Linux-specific shell examples (e.g., Bash), and PowerShell examples are shown in detail, potentially creating friction for Linux/macOS users who do not use PowerShell. However, Azure CLI is cross-platform and shown in every section, so Linux users can complete all tasks.
Recommendations
- Clarify that Azure CLI commands work on Linux, macOS, and Windows, and are the recommended cross-platform approach.
- Consider presenting Azure CLI examples first, before PowerShell, to reinforce CLI as the default for Linux/macOS users.
- Add explicit notes or callouts for Linux/macOS users, such as shell compatibility and installation instructions.
- Remove or de-emphasize PowerShell examples in sections where CLI is sufficient, or move them to secondary tabs.
- Include Bash shell output examples where relevant, to demonstrate Linux parity.
Aks
Handle AKS node upgrades with GitHub Actions
...-docs/blob/main/articles/aks/upgrade-github-actions.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Mention
Summary
The documentation briefly mentions Windows and PowerShell as options for creating an AKS cluster before Linux/CLI alternatives, but all actual examples and workflow steps use Azure CLI and Ubuntu runners, which are cross-platform and Linux-friendly. No Windows/Powershell-only instructions or tools are used for the main workflow.
Recommendations
- List Linux/CLI options before Windows/PowerShell in the 'Before you begin' section to avoid subtle ordering bias.
- Clarify that all steps and examples are cross-platform and can be run from Linux, macOS, or Windows environments.
- If mentioning PowerShell, provide parity by mentioning Bash or other Linux-native shells.
- Consider adding a note that Azure CLI is available on all major platforms.
Aks
Use AMD GPUs on Azure Kubernetes Service (AKS)
.../azure-aks-docs/blob/main/articles/aks/use-amd-gpus.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Mention
Summary
The documentation briefly mentions Windows and Azure PowerShell as options for creating AKS clusters, but all actual usage examples and instructions are Linux-oriented (Azure CLI and bash/kubectl). No Windows-specific tools, examples, or PowerShell commands are provided for the main AMD GPU workflow. The mention of Windows comes before Linux in the list of unsupported OSes and in the cluster creation options, but does not impact the ability of Linux/macOS users to follow the guide.
Recommendations
- List Linux options first when describing cluster creation methods to emphasize Linux parity.
- Clarify that all examples use Azure CLI and bash/kubectl, and provide explicit guidance for users on Windows (e.g., using WSL or Azure CLI for Windows).
- Remove or de-emphasize references to Azure PowerShell unless PowerShell-specific instructions are provided.
- Explicitly state that the workflow is Linux-focused and that Windows node pools are not supported for AMD GPUs.
Aks
Use Azure Policy to secure your Azure Kubernetes Service (AKS) clusters
...re-aks-docs/blob/main/articles/aks/use-azure-policy.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page displays mild Windows bias by listing Windows-specific tools (Azure PowerShell) before Linux equivalents (Azure CLI) when describing how to create an AKS cluster. The prerequisites mention Azure CLI, Azure PowerShell, and Azure portal, but PowerShell is listed before the portal and after CLI, which may subtly prioritize Windows tooling. However, all example commands for interacting with Kubernetes use kubectl, which is cross-platform, and there are no PowerShell-specific examples or Windows-only instructions in the main workflow.
Recommendations
- List Azure CLI and Azure portal before Azure PowerShell in prerequisites to reflect platform neutrality and the CLI's popularity on Linux/macOS.
- Explicitly state that all instructions and kubectl commands work on Linux, macOS, and Windows.
- Consider providing brief notes or links for Linux/macOS users where Azure PowerShell is mentioned, clarifying that Azure CLI is the recommended cross-platform tool.
- Ensure future examples do not default to Windows-first tooling or terminology.
Aks
Upgrade Azure Kubernetes Service (AKS) node images
...-aks-docs/blob/main/articles/aks/upgrade-node-image.md
Low Priority
View Details →
Detected Bias Types
Windows Reference
Windows First
Summary
The documentation is largely cross-platform, using Azure CLI and kubectl commands that work on Linux, macOS, and Windows. However, there are repeated notes referencing Windows and PowerShell environments when discussing shell differences, without equivalent notes or examples for Linux/macOS shells. These notes appear before any mention of Linux/macOS specifics, subtly prioritizing Windows users.
Recommendations
- Add explicit notes or examples for Linux/macOS shell differences where relevant, not just Windows/PowerShell.
- When referencing shell-specific behavior, provide parity by mentioning Bash/zsh (Linux/macOS) alongside Windows/PowerShell.
- If JSONPath or command syntax differs on Linux/macOS, include those examples or clarifications.
- Review the order of platform references to avoid consistently mentioning Windows/PowerShell first.
Aks
Use Microsoft Entra pod-managed identities in AKS (Preview)
...cs/blob/main/articles/aks/use-azure-ad-pod-identity.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation relies exclusively on Azure CLI commands and tools, which are cross-platform but originate from the Windows ecosystem and are most commonly associated with Windows environments. There are no PowerShell-specific examples, but all management and setup instructions use Azure CLI and Azure Portal, with no mention of Linux-specific alternatives or workflows. Examples and instructions do not reference Linux/macOS shell differences, nor do they provide parity for Linux-native tools or package managers (e.g., apt, yum, Homebrew) for installing prerequisites. However, the documentation does note that pod-managed identities are only supported on Linux node pools, and most commands (e.g., kubectl, bash, YAML) are platform-agnostic.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and provide installation instructions for Linux/macOS (e.g., via apt, yum, Homebrew) alongside Windows.
- Include notes or examples for Linux/macOS users where command syntax or environment variables may differ.
- Reference Linux-native workflows for AKS management where applicable (e.g., using bash scripts, cloud-init, etc.).
- Clarify that all examples are valid for Linux/macOS unless otherwise noted, and highlight any platform-specific caveats.
- Consider including troubleshooting tips for Linux/macOS environments, such as permissions, path issues, or shell differences.
Aks
Secure Pod Traffic with Network Policies in Azure Kubernetes Service (AKS)
...ks-docs/blob/main/articles/aks/use-network-policies.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation provides both Linux and Windows coverage for AKS network policies, but Windows-specific instructions (such as preview feature registration and admin credential setup) are more detailed and appear before Linux equivalents in some sections. Windows tooling (e.g., HNS ACLPolicy) is mentioned alongside Linux tools (IPTables), but there is a slight tendency to introduce Windows-specific steps and requirements more prominently. All CLI examples use Azure CLI and Bash, which are cross-platform, but the documentation sometimes foregrounds Windows node pool scenarios and requirements, such as admin credential creation and feature flag registration, before or alongside Linux instructions.
Recommendations
- Ensure Linux instructions and examples are presented first or in parallel with Windows instructions, especially in sections where both are supported.
- Clearly separate Linux and Windows node pool setup steps, making it easy for users to find relevant instructions for their platform.
- Add explicit notes or tables summarizing differences and requirements for Linux vs. Windows, rather than embedding Windows-specific steps in general instructions.
- Where Windows-specific tools (e.g., HNS ACLPolicy) are mentioned, provide equivalent Linux tool references (e.g., IPTables) with equal detail.
- Consider adding PowerShell examples for Windows users, but always provide Bash equivalents for Linux/macOS users.
Aks
Use node taints in an Azure Kubernetes Service (AKS) cluster
...ure-aks-docs/blob/main/articles/aks/use-node-taints.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page mentions Windows tooling (Azure PowerShell) as a primary option for creating an AKS cluster in the prerequisites section, listing it before Linux-native equivalents. However, all command-line examples throughout the document use Azure CLI and kubectl, which are cross-platform and do not show Windows/Powershell-specific commands or patterns. No Windows-only tools or examples are present, and Linux/macOS users can follow all instructions without issue.
Recommendations
- List Linux-native tools (Azure CLI) before Windows-specific tools (Azure PowerShell) in the prerequisites section to avoid implying Windows is the primary platform.
- Explicitly state that all CLI commands are cross-platform and provide links to installation instructions for Azure CLI and kubectl on Linux/macOS.
- If mentioning Azure PowerShell, consider also mentioning Linux-friendly alternatives (e.g., Bash scripts) or clarify that PowerShell is available cross-platform.
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 tools (Azure PowerShell) and the Azure portal as options for creating AKS clusters before Linux-specific instructions, but all actual command-line examples and node pool instructions use Azure CLI and kubectl, which are cross-platform and Linux-friendly. No PowerShell-specific examples are provided, and all operational steps are shown with Linux-compatible commands. There is a slight bias in listing Windows tools as options before Linux equivalents, but no critical impact on Linux/macOS users.
Recommendations
- List Linux-first options (Azure CLI) before Windows tools (PowerShell, portal) when describing how to create clusters.
- Explicitly state that all shown commands work on Linux/macOS and Windows.
- Provide parity in example links or references, e.g., link to Linux/macOS installation guides for Azure CLI and kubectl.
- If mentioning PowerShell, consider also mentioning Bash or zsh for Linux users.
Aks
Trusted Launch with Azure Kubernetes Service (AKS)
...-aks-docs/blob/main/articles/aks/use-trusted-launch.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates mild Windows bias by referencing Windows-centric technologies and documentation links before Linux equivalents, especially in the Secure Boot and TPM sections. Key external links point to Windows documentation, and terminology such as 'signed by trusted publishers' is more familiar in Windows contexts. However, the actual usage instructions and examples are platform-neutral, focusing on Azure CLI and ARM templates, which work on Linux, macOS, and Windows equally. There are no PowerShell-specific examples, nor are there Windows-only commands or tools required for the main workflow.
Recommendations
- Provide equal or greater emphasis on Linux support for Secure Boot and vTPM, including links to Linux documentation (e.g., Ubuntu Secure Boot, Linux TPM usage).
- Where external links reference Windows documentation (e.g., Secure Boot, TPM, attestation), add equivalent links for major Linux distributions.
- Clarify in the Secure Boot section which Linux distributions are supported and provide examples or references for troubleshooting Secure Boot failures on Linux.
- Avoid language that implies Windows is the default or primary platform (e.g., 'Both Windows and select Linux distributions support Secure Boot' could be reworded to highlight Linux support more explicitly).
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 Examples
Summary
The documentation page is generally cross-platform and does not show strong Windows bias. However, there is a minor emphasis on Windows containers as a specific use case, and Windows Server containers are mentioned as a feature. No examples or tooling instructions are provided, so there is no evidence of PowerShell-heavy or Windows-first bias. Linux and macOS users are not excluded from any critical information.
Recommendations
- When mentioning Windows containers as a use case, also highlight Linux container scenarios to maintain parity.
- If future versions of this page add example commands or setup instructions, ensure both Windows (PowerShell/CMD) and Linux/macOS (bash) examples are provided.
- Consider adding a brief note clarifying that AKS supports both Linux and Windows containers, and that most features are available cross-platform.