Generated banner for Azure Kubernetes App Deploy
Generated logo for Azure Kubernetes App Deploy

Azure Kubernetes App Deploy

MicrosoftOfficialCreated by Microsoft

  • Skill
  • Tool integration
  • Cloud and DevOps
  • MIT
  • Low risk

From the author

Use when deploying an existing web application or API to an already-running Azure Kubernetes Service cluster. Detects the framework, generates a Dockerfile and Kubernetes manifests, validates against AKS Deployment Safeguards, and deploys with verification. WHEN: deploy app to AKS, deploy to existing AKS cluster, containerize app for Kubernetes, generate K8s manifests for Azure, set up CI/CD for AKS, my AKS deployment is failing safeguard checks, I have a Django/Express/Spring Boot app to run on AKS. DO NOT USE FOR: creating or provisioning an AKS cluster (use azure-kubernetes), assessing migration to AKS Automatic (use azure-kubernetes-automatic-readiness), or deploying to non-AKS targets like Web Apps, Container Apps, or Functions.
— the description by Microsoft

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill streamlines the deployment of web applications and APIs to an existing Azure Kubernetes Service (AKS) cluster. It performs automated framework detection to identify the application stack, generates appropriate Dockerfiles and Kubernetes manifests, and validates the configuration against AKS Deployment Safeguards. The process includes verification steps to ensure the application is correctly deployed and configured for the target environment.

What it does

  • Detects application frameworks and sub-frameworks from project signal files.
  • Automatically generates Dockerfiles and Kubernetes manifests based on detected project requirements.
  • Validates configurations against AKS Deployment Safeguards (DS001–DS013).
  • Resolves base image tags using floating major versions to maintain security and stability.
  • Detects application ports and health endpoints to configure Kubernetes probes.
  • Provides recovery procedures for deployment failures.

When to use it

  • When you need to deploy an existing web application or API to an active AKS cluster.
  • When you need to containerize a project for Kubernetes deployment.
  • When you need to generate Kubernetes manifests tailored for Azure.
  • When your deployment is failing due to AKS Deployment Safeguard checks.
  • When setting up CI/CD pipelines for applications running on AKS.

Advantages

  • Reduces manual effort in creating container and orchestration configurations.
  • Ensures deployments adhere to established AKS Deployment Safeguards.
  • Maintains up-to-date base images through automated major version resolution.
  • Standardizes health probe and port configuration across different frameworks.

Usage examples

“Deploy my Express application to the existing AKS cluster.”
The agent detects the Node.js framework, generates a Dockerfile and Kubernetes manifests, validates them against AKS safeguards, and initiates the deployment.
“My Spring Boot app deployment is failing AKS safeguard checks.”
The agent analyzes the current configuration against the DS001-DS013 checklist to identify and resolve the specific safeguard violations.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/microsoft/azure-kubernetes-app-deploy/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip azure-kubernetes-app-deploy.zip -d .agents/skills

Documentation by Microsoft

Deploy to AKS

Use when: deploying a web app/API to AKS; containerizing for Kubernetes; generating manifests; AKS CI/CD; DS001–DS013 failures.

Not for: provisioning clusters (azure-kubernetes), AKS Automatic readiness (azure-kubernetes-automatic-readiness), non-AKS targets.

Workflow

Requires: existing AKS cluster, az login, kubectl configured. Follow phases/quick-deploy.md. On failure: references/rollback.md.

References

Knowledge Packs

Load knowledge-packs/frameworks/<framework>.md per detected framework. Available: spring-boot, express, nextjs, fastapi, django, nestjs, aspnet-core, go, flask

Templates

templates/ (dockerfiles/, k8s/, github-actions/, mermaid/).

Files

references/base-images.md

Base Image Policy

How the skill chooses container base images. Goal: no version number is stored in this repo — the concrete tag is resolved when the Dockerfile is generated, so templates never go stale.

Rules

  1. Never pin minor/patch. Use a floating major (or major.minor) tag. Floating tags receive security patches automatically — a frozen patch tag does not.

  2. Resolve <LATEST_STABLE_*> at generation time. When generating a Dockerfile, replace each placeholder with the current stable major the project targets (see "Resolution" below), then keep that major tag in the output. A major tag is concrete, so it satisfies Deployment Safeguard DS009 (no :latest).

  3. Prefer the Microsoft/Azure Linux image when one exists and the project has no reason to avoid it. These are first-party, signed, and rebuilt for CVEs. They are listed below as the preferred option; the current default source is kept for drop-in compatibility.

Per-language images

LanguageDefault source (template today)Tag policyPreferred Microsoft / Azure Linux image
.NETmcr.microsoft.com/dotnet/{sdk,aspnet}floating major (e.g. 9.0)already Microsoft ✓
Javaeclipse-temurin:<maj>-{jdk,jre}-alpinefloating major LTSmcr.microsoft.com/openjdk/jdk:<maj>-azurelinux (also -distroless)
Pythonmcr.microsoft.com/azurelinux/base/python:<maj.min>floating major.minoralready Microsoft ✓
Nodenode:<maj>-alpinefloating major LTSmcr.microsoft.com/azurelinux/base/nodejs:<maj>
Gobuild golang:<ver>-alpine, runtime gcr.io/distroless/static-debian12floating major.minormcr.microsoft.com/oss/go/microsoft/golang:<ver>-azurelinux3.0
Rustbuild rust:<ver>-slim, runtime gcr.io/distroless/cc-debian12floating major.minormcr.microsoft.com/azurelinux/base/rust:<maj.min>

The Go and Rust runtime stages keep the literal gcr.io/distroless/*-debian12 names and do not use a <LATEST_STABLE_*> placeholder: distroless images are identified by base-OS variant (the Debian release), not by language version, and they float their patch level within that Debian release. This asymmetry with the build stages is intentional — don't "fix" it by adding a placeholder.

Adopting the Microsoft Azure Linux images for Node/Go/Rust changes the in-image package manager (tdnf, not apk/apt) and the non-root-user setup. That migration is intentionally out of scope here — this file documents the target so a later change can adopt it.

Resolution

To fill a <LATEST_STABLE_*> placeholder at generation time, in order of preference:

  1. Explicit check. Query the registry or release channel for the current stable major, e.g.:

    • .NET / Java / Go (Microsoft): az acr manifest list-metadata against the MCR repo, or the image's tag list.

    • Python / Node / Rust: the language's published release channel (Docker Hub tag list, or the language's downloads page).

  2. Fallback. If no check is possible (offline, no registry access), use the latest stable major you know, and add a comment in the generated Dockerfile: # verify this is still the current stable major.

Why floating majors are maintenance-free: Microsoft major tags always carry the latest minor and are rebuilt for CVEs on a regular cadence; Docker Hub -slim/-alpine tags float their patch level the same way. A major tag is therefore both stable to reference and current for security.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

What our scanner noticed· Low risk

  • Instructions that use the network

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Microsoft
Publisher
Microsoft (Official)
Source
microsoft/skills · .github/plugins/azure-skills/skills/azure-kubernetes/azure-kubernetes-app-deploy · commit 0696600
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from .github/plugins/azure-skills/LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced
Also distributed in
microsoft/azure-skills

AutoGineer is not affiliated with or endorsed by Microsoft.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download azure-kubernetes-app-deploy.zip