AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

azure-kubernetes-automatic-readiness

Assess Kubernetes workloads and cluster configuration for AKS Automatic compatibility. Identifies incompatibilities, generates fixes, and guides migration from AKS Standard to AKS Automatic. WHEN: migrate to AKS Automatic, check AKS Automatic readiness, validate manifests for Automatic, assess cluster for Automatic compatibility, fix deployment for Automatic compatibility, identify AKS Automatic migration blockers, is my cluster ready for AKS Automatic.

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read microsoft--azure-kubernetes-automatic-readiness at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 4

references/common-fixes.md

Common Fix Patterns for AKS Automatic Compatibility

Loaded on demand when generating YAML fixes during assessment. Maps to constraint IDs in constraint-spec-v1.yaml.


safeguard-container-resource-requests — Add resource requests/limits

Before:

containers:
  - name: web
    image: myapp:v1.0.0

After:

containers:
  - name: web
    image: myapp:v1.0.0
    resources:
      requests:
        cpu: "250m"
        memory: "256Mi"
      limits:
        cpu: "500m"
        memory: "512Mi"

💡 Tip: Use safe minimums as starting values. VPA (auto-enabled on AKS Automatic) will tune these after deployment based on actual usage.


safeguard-container-capabilities — Drop all capabilities

Before:

securityContext:
  capabilities:
    add: ["NET_ADMIN"]

After:

securityContext:
  capabilities:
    drop: ["ALL"]

⚠️ Warning: If the app genuinely requires NET_ADMIN or similar, it is incompatible with AKS Automatic. Do not silently drop — explain the incompatibility and suggest redesign.


safeguard-no-privilege-escalation — Disable privilege escalation (conditional: PSS Restricted)

Apply when the target opts into PSS Restricted or the cluster's active constraints require it; on the default Automatic Baseline this is optional hardening.

Before:

securityContext: {}

After:

securityContext:
  allowPrivilegeEscalation: false

safeguard-allowed-seccomp-profiles — Add seccomp profile

Before:

spec:
  containers:
    - name: web

After:

spec:
  securityContext:
    seccompProfile:
      type: RuntimeDefault
  containers:
    - name: web

safeguard-allowed-seccomp-profiles — Remove 'Unconfined' seccomp profile

Before:

spec:
  securityContext:
    seccompProfile:
      type: Unconfined
  containers:
    - name: web

After:

spec:
  containers:
    - name: web

safeguard-enforce-apparmor — Add AppArmor annotation

Before:

metadata:
  name: my-deployment

After:

metadata:
  name: my-deployment
  annotations:
    container.apparmor.security.beta.kubernetes.io/web: runtime/default

💡 Tip: Replace web with the actual container name. Add one annotation per container.


safeguard-images-no-latest — Pin image tag (LLM-reasoned — ask user)

Before:

image: myapp:latest

After:

image: myapp:v1.2.3   # ← version confirmed with user

⚠️ Warning: Do not guess the version. Ask the user: "What specific version tag or SHA digest should I pin this image to?" If from a public registry, suggest checking Docker Hub or the registry for the latest stable tag.


safeguard-probes-configured — Add probes (best-practice recommendation — warning-only, not blocked at admission)

HTTP app (most common):

readinessProbe:
  httpGet:
    path: /healthz        # ← ask user for their health endpoint
    port: 8080            # ← ask user for port
  initialDelaySeconds: 5
  periodSeconds: 10
  failureThreshold: 3
livenessProbe:
  httpGet:
    path: /healthz
    port: 8080
  initialDelaySeconds: 15
  periodSeconds: 20
  failureThreshold: 3

TCP-only app (databases, Redis, etc.):

readinessProbe:
  tcpSocket:
    port: 6379           # ← service port
  initialDelaySeconds: 5
  periodSeconds: 10
livenessProbe:
  tcpSocket:
    port: 6379
  initialDelaySeconds: 15
  periodSeconds: 20

gRPC app:

readinessProbe:
  grpc:
    port: 50051
  initialDelaySeconds: 5
  periodSeconds: 10

safeguard-host-probes — Remove host field in probes and lifecycle hooks

Advisory only: this rule is not part of the public Deployment Safeguards initiative (c047ea8e) and is not verified as an Automatic admission block. Present it as a recommendation, not a migration blocker.

Before:

spec:
  containers:
  - name: my-container
    image: nginx:v1.2.3
    livenessProbe:
      httpGet:
        host: "my-host"
        path: /healthz
        port: 8080
      initialDelaySeconds: 15
      periodSeconds: 20
      failureThreshold: 3

After: Remove the host field Example:

spec:
  containers:
  - name: my-container
    image: nginx:v1.2.3
    livenessProbe:
      httpGet:
        path: /healthz
        port: 8080
      initialDelaySeconds: 15
      periodSeconds: 20
      failureThreshold: 3

safeguard-pod-enforce-antiaffinity — Add topology spread (LLM-reasoned — ask user for label)

Ask user: "What label key/value identifies your workload's pods?"

spec:
  template:
    spec:
      topologySpreadConstraints:
        - maxSkew: 1
          topologyKey: kubernetes.io/hostname
          whenUnsatisfiable: DoNotSchedule
          labelSelector:
            matchLabels:
              app: <app-label>     # ← from user
      containers:
        - name: web

safeguard-csi-driver-storage-class — Migrate in-tree to CSI

Before (Azure Disk in-tree):

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: fast-storage
provisioner: kubernetes.io/azure-disk
parameters:
  skuName: Premium_LRS
reclaimPolicy: Delete
volumeBindingMode: Immediate

After (Azure Disk CSI):

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: fast-storage
provisioner: disk.csi.azure.com
parameters:
  skuName: Premium_LRS
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer   # ← preferred for zonal disks

| In-tree provisioner | CSI replacement | |---|---| | kubernetes.io/azure-disk | disk.csi.azure.com | | kubernetes.io/azure-file | file.csi.azure.com |


PodDisruptionBudget — Add missing PDB

apiVersion: policy/v1
kind: PodDisruptionBudget
metadata:
  name: <app-name>-pdb
  namespace: <namespace>
spec:
  maxUnavailable: 1
  selector:
    matchLabels:
      app: <app-label>

PodDisruptionBudget — Fix blocking maxUnavailable: 0

Before:

spec:
  maxUnavailable: 0

After:

spec:
  maxUnavailable: 1

⚠️ Warning: maxUnavailable: 0 completely blocks node drain during AKS Automatic upgrades. At least 1 pod must be allowed unavailable for upgrades to proceed.


safeguard-no-host-path-volumes — Replace hostPath (incompatible — suggest alternatives)

| hostPath use case | Recommended replacement | |---|---| | Log collection (/var/log) | Azure Monitor Container Insights (auto-enabled on AKS Automatic) | | Container runtime socket (/var/run/docker.sock) | Use the AKS Automatic node observability features — direct socket access not supported | | Shared config files | configMap volume | | Secrets / credentials | Kubernetes secret volume or Azure Key Vault CSI Driver | | Ephemeral scratch space | emptyDir volume | | Persistent app data | Azure Disk CSI via PVC (disk.csi.azure.com) | | Shared file storage across pods | Azure Files CSI via PVC (file.csi.azure.com) |

emptyDir example:

volumes:
  - name: scratch
    emptyDir: {}

Azure Files CSI PVC example:

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: logs-pvc
spec:
  accessModes:
    - ReadWriteMany
  storageClassName: azurefile-csi
  resources:
    requests:
      storage: 10Gi