# AKS Nodes on Azure | ZopNight

> Every check ZopNight runs on your AKS Nodes on Azure: 4 in total, across reliability. Each one says why it matters and exactly what to change.

Source: https://zop.dev/zopnight/rules/azure/aks-node

---

_Azure · 4 checks_

## AKS Nodes on Azure, checked for you.

ZopNight runs 4 checks on your AKS Nodes in Azure, covering reliability. Workloads are scheduled by namespace.

- 4 — checks
- 1 — category
- Manual — fixes, spelled out
- Yes — scheduled with its namespace

Free to start. No card. The playground just needs your work email.

## Every check, grouped by what it protects.

Each one opens with why it matters and exactly what to change.

### Reliability

Production-shape issues that cause incidents and rework: single replicas, missing requests and limits, missing probes.

- [Node Not Ready](https://zop.dev/zopnight/rules/node-not-ready)
- [Node Under Disk Pressure](https://zop.dev/zopnight/rules/node-under-disk-pressure)
- [Node Under Memory Pressure](https://zop.dev/zopnight/rules/node-under-memory-pressure)
- [Node Under PID Pressure](https://zop.dev/zopnight/rules/node-under-pid-pressure)

## Find these on your own AKS Nodes.

Connect a read-only role and ZopNight inventories the AKS Nodes you run, then runs all 4 checks against them.

[object Object]