WEBVTT 00:00:00.030 --> 00:00:04.255 position:50% align:center size:88% Let's review the recorded return to the previous application version. 00:00:04.305 --> 00:00:08.179 position:50% align:center size:88% We'll separate image redeployment from restoring database content. 00:00:08.659 --> 00:00:10.659 position:50% align:center size:88% Open Rollback context. 00:00:10.734 --> 00:00:14.384 position:50% align:center size:88% This was an approved return to the previous application release. 00:00:14.459 --> 00:00:18.809 position:50% align:center size:88% It followed the completed upgrade on the same rehearsal installation. 00:00:18.884 --> 00:00:22.384 position:50% align:center size:88% Compare the source and target before following the result. 00:00:22.484 --> 00:00:24.318 position:50% align:center size:88% This was an operator-led drill. 00:00:26.320 --> 00:00:28.795 position:50% align:center size:88% Click Pipeline parameters and plan. 00:00:28.870 --> 00:00:32.270 position:50% align:center size:88% Both the previous image and chart versions were selected. 00:00:32.320 --> 00:00:35.620 position:50% align:center size:88% The operator reran the customer deployment pipeline. 00:00:35.695 --> 00:00:38.120 position:50% align:center size:88% This was not a Helm rollback command. 00:00:38.170 --> 00:00:42.320 position:50% align:center size:88% The infrastructure plan reported no changes across nine units. 00:00:42.445 --> 00:00:45.499 position:50% align:center size:88% Scroll between the target fields and that plan result. 00:00:47.520 --> 00:00:50.795 position:50% align:center size:88% Open Signing notice and configuration safeguards. 00:00:50.870 --> 00:00:54.145 position:50% align:center size:88% This is the standing notice from the earlier upgrade record. 00:00:54.220 --> 00:00:57.220 position:50% align:center size:88% That record reports the image as UNVERIFIED. 00:00:57.295 --> 00:01:00.395 position:50% align:center size:88% The rollback's own signing log is not preserved. 00:01:00.470 --> 00:01:04.295 position:50% align:center size:88% The runbook separates image choice from the current secret-key set. 00:01:04.370 --> 00:01:09.195 position:50% align:center size:88% An older Helm revision can contain keys that no longer decrypt data. 00:01:09.295 --> 00:01:12.331 position:50% align:center size:88% This review does not demonstrate a key-rotation test. 00:01:14.360 --> 00:01:16.685 position:50% align:center size:88% Choose Snapshot and data boundary. 00:01:16.735 --> 00:01:20.360 position:50% align:center size:88% The operator records a snapshot named for the rollback target. 00:01:20.435 --> 00:01:24.360 position:50% align:center size:88% The same record dates it before the previous image was redeployed. 00:01:24.435 --> 00:01:28.735 position:50% align:center size:88% It describes database content from the upgraded application era. 00:01:28.810 --> 00:01:32.635 position:50% align:center size:88% Returning an image does not restore database content. 00:01:32.710 --> 00:01:35.544 position:50% align:center size:88% A data restore would require its own evidence. 00:01:37.480 --> 00:01:39.930 position:50% align:center size:88% Click Recorded result and read checks. 00:01:39.980 --> 00:01:43.830 position:50% align:center size:88% The saved output names the rollback run and marks it succeeded. 00:01:43.905 --> 00:01:47.255 position:50% align:center size:88% Beside it, saved health data names the previous build. 00:01:47.305 --> 00:01:51.455 position:50% align:center size:88% The operator records revision three and successful workspace reads. 00:01:51.530 --> 00:01:55.405 position:50% align:center size:88% Upgrade complete refers to redeploying through the pipeline. 00:01:55.480 --> 00:01:58.749 position:50% align:center size:88% These records do not establish complete tenant recovery. 00:02:00.720 --> 00:02:03.070 position:50% align:center size:88% Open Roll-forward and later health. 00:02:03.145 --> 00:02:06.795 position:50% align:center size:88% The later pipeline run also has a saved succeeded result. 00:02:06.870 --> 00:02:10.220 position:50% align:center size:88% A health check before it finished still showed the previous build. 00:02:10.295 --> 00:02:14.933 position:50% align:center size:88% After it finished, a new response named 0.1.108. 00:02:15.008 --> 00:02:19.008 position:50% align:center size:88% Both health responses carry their own observation timestamps. 00:02:19.083 --> 00:02:22.958 position:50% align:center size:88% These readings do not establish smoke or complete recovery. 00:02:23.083 --> 00:02:25.818 position:50% align:center size:88% Scroll back to compare the three recorded runs.