Document Details
Policy For Kubernetes
This page contains Windows bias
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
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates several forms of Windows bias. Windows tools (Azure portal, Azure CLI, Azure PowerShell) are consistently presented as the primary or only method for cluster and policy management, with PowerShell commands included for resource provider registration. Instructions for using the Azure portal (a Windows-centric tool) are given before CLI alternatives. There are no explicit Linux shell or native Linux tool examples for resource provider registration, and the documentation does not mention Linux-specific patterns (e.g., bash scripting for automation, package managers for CLI installation). The page also references Windows domains and endpoints, and only briefly mentions Linux in the context of node pool support and pod security. There are no examples or guidance for Linux users who may prefer non-Microsoft tooling or workflows.
Recommendations
- Provide Linux-native instructions for resource provider registration and other setup steps, such as using bash scripts or REST API calls.
- Include examples for installing and managing Azure CLI on Linux distributions, and reference package managers like apt, yum, or zypper.
- Offer parity for PowerShell commands by providing equivalent bash or shell script examples.
- Clarify that Azure CLI and kubectl are cross-platform and provide explicit instructions for Linux users (e.g., installation, environment setup).
- Mention and link to Linux-specific troubleshooting resources and best practices.
- When listing portal and CLI options, alternate the order or explicitly state that both Windows and Linux users are supported.
- Expand the FAQ and limitations sections to address Linux-specific scenarios, such as SELinux/AppArmor interactions, and clarify any differences in policy enforcement or logging on Linux clusters.
Create Pull Request
Scan History
| Date | Scan | Status | Result |
|---|---|---|---|
| 2026-01-14 00:00 | #250 | in_progress |
Biased
|
| 2026-01-13 00:00 | #246 | completed |
Biased
|
| 2026-01-11 00:00 | #240 | completed |
Biased
|
| 2026-01-10 00:00 | #237 | completed |
Biased
|
| 2026-01-09 00:34 | #234 | completed |
Biased
|
| 2026-01-08 00:53 | #231 | completed |
Biased
|
| 2026-01-06 18:15 | #225 | cancelled |
 Clean
|
| 2025-09-03 00:00 | #100 | completed |
Clean
|
| 2025-08-29 00:01 | #95 | completed |
Clean
|
| 2025-08-27 00:01 | #93 | cancelled |
Clean
|
| 2025-08-26 00:00 | #92 | cancelled |
Clean
|
| 2025-08-25 00:01 | #91 | cancelled |
Clean
|
| 2025-08-24 00:00 | #90 | cancelled |
Clean
|
| 2025-08-22 00:01 | #88 | completed |
Clean
|
| 2025-08-21 00:01 | #87 | cancelled |
Clean
|
| 2025-08-20 00:01 | #86 | completed |
Clean
|
| 2025-08-19 00:01 | #85 | completed |
Clean
|
| 2025-08-17 00:01 | #83 | cancelled |
Clean
|
| 2025-08-07 00:00 | #73 | completed |
Clean
|
| 2025-08-06 00:00 | #72 | completed |
Clean
|
| 2025-08-05 00:00 | #71 | completed |
Clean
|
| 2025-08-03 00:00 | #69 | completed |
Clean
|
| 2025-08-01 00:00 | #67 | completed |
Clean
|
| 2025-07-31 00:00 | #66 | completed |
Clean
|
| 2025-07-30 00:00 | #65 | completed |
Clean
|
| 2025-07-29 00:01 | #64 | completed |
Clean
|
| 2025-07-28 00:00 | #63 | completed |
Clean
|
| 2025-07-27 00:00 | #62 | completed |
Clean
|
| 2025-07-26 00:01 | #61 | completed |
Clean
|
| 2025-07-25 00:00 | #60 | completed |
Clean
|
| 2025-07-24 00:00 | #59 | completed |
Clean
|
| 2025-07-23 00:00 | #58 | completed |
Clean
|
| 2025-07-22 00:01 | #57 | completed |
Clean
|
| 2025-07-21 00:00 | #56 | completed |
Clean
|
| 2025-07-19 13:51 | #54 | completed |
Clean
|
| 2025-07-17 00:00 | #53 | completed |
Biased
|
| 2025-07-16 00:00 | #52 | completed |
Biased
|
| 2025-07-13 21:37 | #48 | completed |
Clean
|