Retention and recovery overview

Guidance for retaining operator-facing assets, validating recent visibility windows and checking the portal after a redeploy.

RetentionRecoveryValidation
Docs homeConceptsPlatform structureOperator guideTroubleshootingSecurityReference

What to retain

  • Keep the current portal revision and at least two prior revisions.
  • Retain matching release notes so field changes can be correlated with operator behavior.
  • Review contact details and security references during regular documentation maintenance.

Visibility windows

Operators usually care about three visibility windows: recent events, current workload state and current image metadata. If one of these windows is unexpectedly empty or stale after a redeploy, validate routing and data-source reachability before assuming object health changed.

Recovery checks

  1. Open the portal and confirm navigation works across overview, observability, registry and docs.
  2. Validate that summary cards, tables and drawers render correctly.
  3. Review custom 403/404 behavior and access-check messaging.
  4. Confirm documentation links and related-object navigation still resolve.
← Environment compatibilityDocumentation center →