# AKS CronJobs on Azure | ZopNight

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

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

---

_Azure · 3 checks_

## AKS CronJobs on Azure, checked for you.

ZopNight runs 3 checks on your AKS CronJobs in Azure, covering governance. Workloads are scheduled by namespace.

- 3 — 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.

### Governance

Missing tags and labels that break cost attribution, such as no environment, team or cost-centre value.

- [CronJob Allows Concurrent Runs](https://zop.dev/zopnight/rules/cronjob-allows-concurrent-runs)
- [CronJob Never Scheduled](https://zop.dev/zopnight/rules/cronjob-never-scheduled)
- [Suspended CronJob](https://zop.dev/zopnight/rules/suspended-cronjob)

## Find these on your own AKS CronJobs.

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

[object Object]