Administer · v0.0.1

Support and escalation handoff

Collect a complete, secret-safe case that another operator can continue without reconstructing the incident.

AudienceOperators · support coordinatorsReading time10 minutesCommands in context1 guided stepsReviewed sourcefcc5871 · 30 July 2026

Exact release scope. This page documents the reviewed v0.0.1 source at fcc5871. Check release status before enabling a gated capability.

Minimum case data

Area	Include
Business impact	Affected environment, users/workload, start time, current risk and change freeze
Release	Version, full commit/build identity, chart/bundle and image digests
Topology	Profile, replica counts, provider, agent and dependency identities
Failure	Exact UTC, route/action, HTTP status, error_code, nextAction and correlation ID
Operation	Run, step, attempt, command, cluster, infrastructure and provider action IDs
Evidence	Artifact IDs/checksums, sanitized logs, health snapshots and audit export
Actions	Everything attempted, outcome, retry/idempotency keys and current state

Never attach

Suggested severity

Severity	Use when
SEV-1	Confirmed widespread production outage, destructive integrity risk or active secret/security exposure
SEV-2	Production capability unavailable or unsafe with no acceptable workaround
SEV-3	Degraded/non-production workflow with bounded workaround or documentation gap
SEV-4	Question, evaluation assistance or planned improvement

Copyable case template

Command

Impact:
Environment / workspace:
Release / commit / image digests:
Profile / provider / agent:
UTC first seen:
Action and route:
HTTP status / error_code / nextAction:
Run / step / command / cluster / correlation IDs:
Current durable state:
Evidence artifact IDs and checksums:
Actions already attempted:
Requested decision or help:
Secret review completed by:

Commands for this step

Generate the secret-safe support bundle

Run the canonical redacting collector before opening a support case, then review the bundle manually for customer-specific sensitive data.

Run in orderComplete each step successfully before continuing.

01
Changes statePowerShell
Create a secret-safe support bundle
Create and download a bounded support export without embedding the authenticated session or CSRF token in shell history.
Before you run it
- Approved support case
- Authenticated administrator session
- Support export permission
- Protected output directory
PowerShell · support-bundle-script
```
$sessionCookie = Read-Host "Session cookie" -MaskInput
$csrfToken = Read-Host "CSRF token" -MaskInput
& ./scripts/get-support-bundle.ps1 `
  -BaseUrl https://clusterpilot.example.com `
  -SessionCookie $sessionCookie `
  -CsrfHeaderName X-ClusterPilot-Csrf `
  -CsrfToken $csrfToken `
  -LogHours 24 `
  -OutputPath ./artifacts/clusterpilot-support-bundle.zip `
  -PollIntervalSeconds 5 `
  -TimeoutSeconds 120
Remove-Variable sessionCookie,csrfToken
```
Expected result
The asynchronous job completes and a redacted ZIP is saved; raw session material is not written to the bundle.
Stop conditions and operator notes
- Add -SkipRecentLogs when log export is not approved.
- Inspect the archive before sharing and follow the support-handoff redaction checklist.
Reviewed sourcescripts/get-support-bundle.ps1