Azure Kubernetes Service (AKS) and 7 More Manifest Families — 40 Snippets + 28 Rules That Name a Removed apiVersion, a :latest Tag or a Literal Secret Before It Reaches the Cluster

Your editor does not reject a removed apiVersion. The cluster does, at deploy time. 40 snippets written against the current API versions across 8 file families, and 28 rules that name every removed version, every literal credential and every unpinned image tag sitting in the file you have open.

Install free

Free for the file open in your editor - no key, no limit. The workspace sweep and the report ask for a key.

VS Code MarketplacenpmMCP server (npx)Docker Hub
ext install ReadyStack.cloud-manifest-audit-kit
npx @readystack/cloud-manifest-audit-kit <file>
npx @readystack/cloud-manifest-audit-kit --mcp

Team? One key for every ReadyStack linter, 5 seats, $149 once

Get the full rule table as a PDF
All 28 rules Manifest Snippets + Removed-API Audit (8 Sets) checks, each with its source and date, on printable pages you can hand to your team or auditor. We email it now, and once more only if a rule changes. No newsletter.

Get the full version $29

The same 28 rules run across every file in the workspace instead of one, your team's own banned registries and required labels are checked alongside them, and the findings leave as a CSV, JSON or HTML report file you can attach to the change request

One payment, one licence key for this tool. The key is shown right after payment.

Managed Kubernetes security platforms start at $45 per developer per month; a 2026 cloud security-audit hour benchmarks at $275, and a productized cluster audit starts at GBP 395

Buy the full version — $29
ENDEJAESPT

Find a tool

· ReadyStack

Worked example

Real numbers from this tool, line by line.

Your editor does not reject a removed apiVersion. The cluster does.

Your editor does not reject a removed apiVersion. The cluster does, at deploy time.

That gap is where the outage lives. A PodDisruptionBudget still written against policy/v1beta1 looks perfectly fine in the editor - correct YAML, correct indentation, no squiggly line anywhere. Then AKS moves your cluster to a version that no longer serves that group, the object is refused, and the workload you thought was protected has no disruption budget for the whole of the next node drain.

The timing is not up to you. AKS supports a GA Kubernetes version for twelve months, and when a cluster is about to fall out of the support window it is upgraded automatically to stay inside policy. You can configure the upgrade to stop when deprecated APIs are detected, which is the good outcome: your upgrade halts instead of your CronJob silently never running again.

So the useful moment to catch these lines is while you are typing them, not in CI after the push.

This pack puts twenty-eight rules in the editor. They run on the file you have open and report line numbers:


apiVersion: policy/v1beta1        # removed - the cluster refuses this object
apiVersion: batch/v1beta1         # removed - the schedule silently stops
image: registry.internal/api:latest   # you cannot tell the failing build from the working one
serviceAccountName: default       # shared by every pod in the namespace
runAsUser: 0                      # a root process writes to any volume it has mounted
DB_PASSWORD: hunter2supersecret   # committed once, it exists in every clone forever
# what the snippets give you instead
apiVersion: policy/v1
kind: PodDisruptionBudget
spec:
  minAvailable: 2
  selector:
    matchLabels:
      app.kubernetes.io/name: checkout-api

The rules cover eight file families, not one - Kubernetes and Helm, Azure IoT Edge deployment manifests, MicroProfile and Liberty config, T-SQL, MAUI project files and R scripts - because the engineer who owns the cluster usually owns those repos too. Forty snippet blocks expand at the cursor, all written against API versions that still exist.

Checking the file you have open is free and complete. All twenty-eight rules run, nothing is held back, nothing is watermarked. What a licence changes is scale, not quality: the same rules across every file in the workspace, your team's own banned registries and required labels checked alongside the built-in set, and the findings written out as a CSV, JSON or HTML file you can attach to the change request.

A managed Kubernetes security platform starts around $45 per developer per month. A cloud security-audit hour benchmarks at $275 in 2026. This is $29, once.

15 seconds — what it actually does

Questions people ask

What does the Removed-API Audit actually do?

It reads the manifest you have open and reports, with line numbers, every apiVersion the cluster no longer serves, every literal credential, every :latest image tag and every setting that costs you an outage during a node drain. Twenty-eight rules run on the open file. Forty snippet blocks expand at the cursor, written against the API versions that still exist.

Who is this for?

Platform and DevOps engineers who own Kubernetes or AKS manifests, Helm charts and values files, Azure IoT Edge deployment manifests, MicroProfile and Liberty config, T-SQL scripts, MAUI project files and R analysis scripts. Eight file families in one pack, because the person who owns the cluster usually owns all eight of those repos too.

Why not just use kubectl or a free CLI scanner?

Free scanners run in a terminal or in CI, which means they speak after you have committed and pushed. This runs in the editor, on the line, while you are still writing it. It also carries the eight-family rule set in one place instead of one tool per language, and none of the free scanners know your team's banned registries.

What is free and what needs a licence?

Free is complete for one file: the open manifest is checked against all twenty-eight rules with nothing held back, and all forty snippets expand. A licence changes the scale, not the quality. It runs the same rules across every file in the workspace, adds your team's own rules, and writes the findings out as a report file.

How does the price compare to the alternatives?

Managed Kubernetes security platforms start around forty-five dollars per developer per month, and a 2026 cloud security-audit hour benchmarks at two hundred and seventy-five dollars. A productized cluster audit starts near three hundred and ninety-five pounds. This is twenty-nine dollars once, for the editor-side check that catches the line before review.

Ask about this tool

One question, answered by the person who built it. Your email only if you want the answer sent.

Embed this tool on your site (free)

Paste this code into your page. It runs in your visitor’s browser and stays up to date. Nothing your visitors type is stored.

 All embeddable tools

For businesses: your name and logo instead of ours, and each visitor’s result + e-mail in your inbox (only when they tick consent) — Pro from $19/month. See Pro →