Runbook AKS de nuit pour les structures de soins

Quand l’application de dossier de soins tombe la nuit, l’équipe n’a pas besoin d’un cours Kubernetes. Elle doit savoir si l’écran de dossier, la transmission, les médicaments ou les rondes sont touchés. Les objets sont l’alerte, l’écran, la liste d’appel, Service Health, les nœuds AKS et l’heure du prochain message.

Key Points

• Regarde d’abord qui est touché et quel flux est bloqué.
• Claude Code range alertes nettoyées, kubectl, Service Health et contacts.
• Les humains décident sécurité, papier, familles, vendor et rollback.
• Le runbook donne la prochaine mise à jour, pas seulement un diagnostic.
• Mesure minutes avant premier message, impact, notes sans données personnelles et récidives.

Night Incident Workflow

Les artefacts sont texte d’alerte, heure, écran touché, rapport de nuit, Azure Service Health, Container insights, snapshot kubectl et ordre de contact. Le workflow relie impact métier et signaux AKS.

Official 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. Related internal guide: Kubernetes deployment guide.

What Claude Code Handles And What Humans Decide

Donne à Claude Code des alertes anonymisées, nombre de nœuds, état des pods, namespace, dernier déploiement, Service Health, rôles de contact et rollback. Ne donne pas noms, notes de soin, données médicales, adresses ou téléphones famille.

Claude Code organizes alert text, impact scope, contact order, privacy-safe vendor note, kubectl check list, and missing update time. Humans decide care safety, paper fallback, family or care manager contact, privacy boundary, vendor escalation, rollback, and recovery announcement.

3 Use Cases

Use case 1: Create the first night memo

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

Use case 2: Create 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 privacy-safe vendor note

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

Copy-Paste Prompt

Act as a night incident runbook reviewer for a care provider using AKS.
Organize alerts, impact, Service Health, kubectl snapshot, contact order, privacy-safe vendor note, rollback, and next update time.
Do not run destructive commands.
Remove resident names, care records, medical data, addresses, and phone numbers.
Return the five rows to 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.");
}

Pitfall: Common Failure Cases

Do not answer night staff with only technical terms. Pair AKS state with the affected screen, paper fallback, and next update time. Do not skip Service Health. Do not share personal data with vendors. Do not trust an old contact sheet. Fix the runbook with Service Health, impact scope, sanitized note, contact order, rollback, and update time.

FAQ

Q. Is AKS too much for care operations?

A. It may be too much for a simple record app. It fits when Kubernetes is already used, multiple services exist, or night recovery matters.

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. Minutes to first update, impact confirmation time, privacy-safe vendor notes, repeat incidents, and missed records.

Training And Consultation Signal

If night incidents create unclear calls and privacy-risky notes, AKS operations and incident runbooks are a fit for formation ClaudeCodeLab.

What I Verified

I checked official AKS and Service Health sources, 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 memo.