Azure AKS Windows Containers

Published
Length
3 min read

Luis Felipe Dias

All posts

You run azure aks windows containers by adding a Windows node pool to your cluster. You always need a Linux system node pool first to run core cluster services. Teams often set up these mixed clusters fast to move older Windows apps into cloud pods. During this rush, engineers often grant broad cluster roles so developers can test and fix apps. Broad roles let too many people run commands inside live Windows pods or read sensitive keys. How native roles work for azure aks windows containers K

Your coding agents run with your access.

Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.

You run azure aks windows containers by adding a Windows node pool to your cluster. You always need a Linux system node pool first to run core cluster services. Teams often set up these mixed clusters fast to move older Windows apps into cloud pods. During this rush, engineers often grant broad cluster roles so developers can test and fix apps. Broad roles let too many people run commands inside live Windows pods or read sensitive keys.

How native roles work for azure aks windows containers

Kubernetes uses role-based rules to control who can touch your Windows and Linux workloads. Every rule in this system is purely additive, which means there are no deny rules. You start with zero access and add permissions through roles. A standard Role sets permissions inside one single namespace. A ClusterRole is not tied to one namespace and covers the whole cluster. You can use a ClusterRole to manage cluster-wide items like nodes or resources across all namespaces.

Once you define a Role or ClusterRole, you connect it to users with a binding. A RoleBinding grants permissions inside one namespace. It can point to a Role in that same namespace or a shared ClusterRole. A ClusterRoleBinding grants access across the entire cluster at once. For Windows apps, teams do best when they place pods in their own namespace. Then they use a RoleBinding to keep developer permissions locked inside that one namespace.

Controlling pod logs and shell commands on Windows nodes

Managing pod deployment is only half the job when you run Windows workloads. Engineers also need to read app logs and open shells to fix live bugs. In the Kubernetes API, logs and shell sessions are subresources under the main pod resource. Rules write these subresources with a slash, such as pod logs or pod exec.

If you grant broad pod verbs, users may gain shell access to every Windows container. You must list the log subresource by itself if a user only needs to read output. You should keep the exec subresource restricted to a tiny group of operators. When someone opens a shell into a Windows container, they run commands as the container user. If that container holds database keys or storage credentials, the user can read them right away.

Azure RBAC + AKS Managed Identity: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

What native cluster roles solve and what they leave open

Native Kubernetes roles and bindings do a good job of guarding the cluster API door. They decide which user or group can view pods, read logs, or start a shell session. Using separate namespaces and tight role bindings keeps teams from touching the wrong Windows apps.

Still, native roles stop checking once the API server approves the initial request. A role binding decides who can open a shell, not what commands they run inside it. Native RBAC cannot approve a single command or block a risky PowerShell script in flight. It also cannot mask sensitive fields like emails, phone numbers, card numbers, or national IDs in output. Teams that need command-level checks and data masking must look beyond static cluster roles.

Add request guardrails and response masking beside Kubernetes

Cluster roles and service accounts govern who reaches the Kubernetes API. Still, a broad role or agent can delete workloads or print sensitive values from ConfigMaps and logs. In practice, hoop.dev runs beside the API server as a sidecar for your Kubernetes API and checks every request and response alongside RBAC.

With hoop.dev Kubernetes controls, guardrails can allow listing Secret names while refusing reads of Secret data before execution. Data masking redacts matched keys in returned JSON responses and log streams in memory. Furthermore, hoop.dev holds SOC 2 Type II and is MIT licensed on GitHub.

Frequently asked questions

Can you run a cluster with only Windows nodes in Azure?

No, every cluster needs at least one Linux node pool to run core system pods. You add Windows node pools alongside the Linux pool to host your Windows apps.

How do you let developers read Windows pod logs without giving shell access?

Create a Role in the app namespace that grants get and list on the pod log subresource. Do not include the pod exec subresource in that role.

Can you use a deny rule in Kubernetes RBAC to block Windows node changes?

No, Kubernetes RBAC rules are purely additive and do not support deny rules. To block access, you must avoid granting the permission in any bound Role or ClusterRole.

The query runs. The emails stay hidden.