AKS Night Incident Runbook for Care Providers With Claude Code

When a care record app fails during a night shift, staff do not need a Kubernetes lecture first. They need to know whether resident records, handover notes, medication checks, or shift reports are affected. The concrete artifacts are the alert, care record screen, contact sheet, Service Health state, AKS node status, pod restart count, and next staff update time.

This article shows how a care provider can use Claude Code to turn AKS incident facts into a night-shift contact runbook. The goal is not to let AI recover production. The goal is to organize sanitized alerts, impact, kubectl snapshots, privacy rules, contact order, rollback, and vendor escalation so humans can decide.

Key Points

• In care operations, the first question is who is affected and what workflow is stopped.
• Claude Code can organize sanitized alerts, kubectl summaries, Service Health notes, contact roles, and rollback notes.
• Humans decide resident safety, paper fallback, family or care manager communication, vendor escalation, and recovery approval.
• The runbook should produce the next staff update time, not just a technical diagnosis.
• Measure minutes to first update, impact confirmation time, privacy-safe vendor notes, repeat incidents, and missed records after recovery.

Night Incident Workflow

The concrete artifacts are alert text, incident time, affected screen, night shift report, Azure Service Health, Container insights, kubectl snapshot, and contact order. Microsoft Learn positions AKS as managed Kubernetes and recommends reliability, monitoring, and troubleshooting practices for production workloads.

Primary sources checked: What is AKS?, AKS best practices, deployment and cluster reliability best practices, enable monitoring for AKS, Azure Service Health overview, AKS troubleshooting documentation, node NotReady troubleshooting, and high CPU in AKS. For basic Kubernetes release flow, see Kubernetes deployment guide.

What Claude Code Handles And What Humans Decide

Give Claude Code redacted alert text, node count, pod state, namespace, recent deployment time, Service Health status, contact roles, and rollback candidates. Do not provide resident names, care records, medical notes, addresses, family phone numbers, or private staff contacts.

Claude Code can organize the memo, ask for missing impact scope, draft contact order, produce a privacy-safe vendor note, list kubectl checks, and find missing update times. Humans decide resident safety, paper fallback, family or care manager contact, privacy boundaries, vendor escalation, rollback execution, and recovery announcement.

3 Use Cases

Use case 1: Create the first night-shift memo

• Input: alert text, incident time, affected screen, staff report, Service Health status.
• Output: impact scope, next update time, paper fallback condition, manager update.
• Human review: resident safety, medication or rounds impact, family contact, on-call decision.

Use case 2: Create the technical kubectl snapshot table

• Input: kubectl get nodes, kubectl get pods, describe output, previous logs, recent release time.
• Output: Node NotReady, CrashLoopBackOff, high CPU, network clue, recent change table.
• Human review: production command, restart, rollback, vendor escalation, Azure permission.

Use case 3: Draft a privacy-safe vendor escalation

• Input: redacted incident memo, affected screen, count, time, checked commands, contact role.
• Output: vendor note, reproduction conditions without personal data, next update time, request.
• Human review: resident names removed, contract scope, urgency, phone escalation.

Copy-Paste Prompt

Act as a night incident runbook reviewer for a care provider.
The system is a care record app or internal portal running on AKS.
Goal: organize alerts, impact, Service Health, kubectl snapshots, contact order, privacy-safe vendor notes, and rollback conditions.
Do not run kubectl delete, restart, or rollback commands.
Remove resident names, care records, medical data, addresses, and family phone numbers.
Return the five rows the team should fix today.

Working Check Code

// verify-aks-night-incident-runbook.mjs
// No dependencies. Run with: node verify-aks-night-incident-runbook.mjs
const incidentMemo = {
  industry: "care",
  service: "night-shift-care-record",
  detectedAt: "22:18",
  alert: "AKS node NotReady and pod restart spike",
  serviceHealthChecked: false,
  affectedUsers: "unknown",
  kubectlSnapshot: {
    nodesNotReady: 2,
    podsCrashLooping: 3,
    highCpuPods: 1,
    recentDeployWithinHours: 2
  },
  contactOrder: [
    { role: "night shift lead", name: "Sato", phone: "" },
    { role: "system owner", name: "", phone: "080-0000-0000" },
    { role: "vendor", name: "Cloud partner", phone: "03-0000-0000" }
  ],
  personalDataShared: true,
  rollbackNote: "",
  nextUpdateMinutes: 0
};

const problems = [];

if (!incidentMemo.serviceHealthChecked) {
  problems.push({ item: "Azure Service Health", fix: "check Service Health before blaming the application" });
}
if (incidentMemo.affectedUsers === "unknown") {
  problems.push({ item: "affected users", fix: "write whether staff, managers, families, or residents are affected" });
}
if (incidentMemo.kubectlSnapshot.nodesNotReady > 0) {
  problems.push({ item: "node NotReady", fix: "capture node count, last change time, and network or CPU clues" });
}
if (incidentMemo.kubectlSnapshot.podsCrashLooping > 0) {
  problems.push({ item: "pod restart", fix: "capture namespace, deployment, previous logs, and recent release" });
}
for (const contact of incidentMemo.contactOrder) {
  if (!contact.name || !contact.phone) {
    problems.push({ item: "contact: " + contact.role, fix: "write name and phone before the night shift" });
  }
}
if (incidentMemo.personalDataShared) {
  problems.push({ item: "personal data", fix: "remove resident names and care details from vendor escalation notes" });
}
if (!incidentMemo.rollbackNote) {
  problems.push({ item: "rollback", fix: "write rollback or safe read-only mode before escalation" });
}
if (incidentMemo.nextUpdateMinutes <= 0) {
  problems.push({ item: "next update", fix: "write the next staff update time, such as 15 or 30 minutes" });
}

if (problems.length > 0) {
  console.table(problems);
  process.exitCode = 1;
} else {
  console.log("AKS night incident memo passed.");
}

This script checks Service Health, affected users, Node NotReady, pod restarts, contact order, personal data, rollback, and next update time. In real operations, combine Azure Portal, Container insights, Azure Monitor alerts, kubectl, Log Analytics, and paper fallback records.

Pitfall: Common Failure Cases

The first failure is sending technical terms back to night staff. Fix it by pairing AKS state with the affected care screen, paper fallback condition, and next update time.

The second failure is skipping Azure Service Health. Fix it by checking platform state, AKS alert, recent deployment, and network changes before blaming the application.

The third failure is sharing personal data with a vendor during escalation. Fix it by using screen name, time, count, error text, and checked commands instead of resident details.

The fourth failure is an outdated contact sheet. Fix it with a monthly review of name, role, phone, backup contact, and available hours.

FAQ

Q. Is AKS too much for a care provider?

A. It may be too much for a simple record app. It becomes relevant when the provider already runs Kubernetes, has multiple internal services, needs monitoring, or has night-shift recovery requirements.

Q. Can Claude Code read incident logs?

A. Yes, after removing resident names, care notes, medical details, addresses, phone numbers, and credentials.

Q. What should the team inspect first?

A. Affected screen, Service Health, Node NotReady, pod restarts, and next update time.

Q. What metric matters?

A. Use minutes to first update, impact confirmation time, privacy-safe vendor notes, repeat incidents, and missed records after recovery.

Training And Consultation Signal

If night incidents keep producing unclear calls, privacy-risky messages, and inconsistent vendor explanations, AKS operations and incident runbooks are a fit for ClaudeCodeLab training.

What I Verified

I checked Microsoft Learn references for AKS overview, best practices, cluster reliability, monitoring, Service Health, troubleshooting, Node NotReady, and high CPU. I also checked CTA, executable JavaScript, internal link, external links, locale coverage, and queue removal. The first action is to add affected screen, Service Health, contact order, rollback, and next update time to the night incident memo.