# AKS Services on Azure | ZopNight

> Every check ZopNight runs on your AKS Services on Azure: 4 in total, across reliability and security.

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

---

_Azure · 4 checks_

## AKS Services on Azure, checked for you.

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

- 4 — checks
- 2 — categories
- 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.

- [LoadBalancer Service Stuck Pending](https://zop.dev/zopnight/rules/loadbalancer-service-stuck-pending)

### Security

Risky configurations: privileged containers, containers running as root, host networking, ingress without TLS.

- [Service Has externalIPs Set](https://zop.dev/zopnight/rules/service-has-externalips-set)
- [Service Type LoadBalancer](https://zop.dev/zopnight/rules/service-type-loadbalancer)
- [Service Type NodePort](https://zop.dev/zopnight/rules/service-type-nodeport)

## Find these on your own AKS Services.

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

[object Object]