From ab76972c0e349dbfd27097abec74c5f5f0af0dc8 Mon Sep 17 00:00:00 2001 From: Sang Jun Bak Date: Wed, 19 Nov 2025 19:03:58 -0500 Subject: [PATCH 1/2] docs: Add instructions for cancelling an in-progress rollout --- doc/user/content/installation/_index.md | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/doc/user/content/installation/_index.md b/doc/user/content/installation/_index.md index aea86cb8a07cb..55dd95f8214ff 100644 --- a/doc/user/content/installation/_index.md +++ b/doc/user/content/installation/_index.md @@ -175,6 +175,29 @@ kubectl get materialize -n materialize-environment -w # Check the logs of the operator kubectl logs -l app.kubernetes.io/name=materialize-operator -n materialize ``` + +### Cancelling the Upgrade +To cancel an in-progress rollout and revert to the last completed rollout state, first retrieve the last rollout request ID from your Materialize CR. You can do this with the following command: + +```shell +kubectl get materialize -n materialize-environment -o jsonpath='{.status.lastCompletedRolloutRequest}' +``` + +Next, get the previous `environmentdImageRef` from the `last-applied-configuration` annotation: +```shell +kubectl get materialize -n materialize-environment -o jsonpath='{.metadata.annotations.kubectl\.kubernetes\.io/last-applied-configuration}' +``` +Finally, run the following command using the values obtained above: + +```shell +kubectl patch materialize \ + -n materialize-environment \ + --type='merge' \ + -p "{\"spec\": {\"requestRollout\": \"\", \"environmentdImageRef\": \"\" }}" +``` + + + ### Version Specific Upgrade Notes #### Upgrading to `v26.0` From 02837677f6495c0660d6b0c883be29601d39c1ac Mon Sep 17 00:00:00 2001 From: Sang Jun Bak Date: Fri, 21 Nov 2025 16:34:38 -0500 Subject: [PATCH 2/2] docs: Clarify instructions for cancelling an in-progress rollout --- doc/user/content/installation/_index.md | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/doc/user/content/installation/_index.md b/doc/user/content/installation/_index.md index 55dd95f8214ff..f59769f684cd8 100644 --- a/doc/user/content/installation/_index.md +++ b/doc/user/content/installation/_index.md @@ -177,23 +177,22 @@ kubectl logs -l app.kubernetes.io/name=materialize-operator -n materialize ``` ### Cancelling the Upgrade -To cancel an in-progress rollout and revert to the last completed rollout state, first retrieve the last rollout request ID from your Materialize CR. You can do this with the following command: + +You may want to cancel an in-progress rollout if the upgrade has failed. This may be indicated by new pods not being healthy. Before cancelling, verify that the upgrade has not already completed by checking that the deploy generation (found via `status.activeGeneration`) is still the one from before the upgrade. Once an upgrade has already happened, you cannot revert using this method. + +To cancel an in-progress rollout and revert to the last completed rollout state, first retrieve the last rollout request ID from your Materialize CR: ```shell kubectl get materialize -n materialize-environment -o jsonpath='{.status.lastCompletedRolloutRequest}' ``` -Next, get the previous `environmentdImageRef` from the `last-applied-configuration` annotation: -```shell -kubectl get materialize -n materialize-environment -o jsonpath='{.metadata.annotations.kubectl\.kubernetes\.io/last-applied-configuration}' -``` -Finally, run the following command using the values obtained above: +Then, set the `requestRollout` back to this value: ```shell kubectl patch materialize \ -n materialize-environment \ --type='merge' \ - -p "{\"spec\": {\"requestRollout\": \"\", \"environmentdImageRef\": \"\" }}" + -p "{\"spec\": {\"requestRollout\": \"\"}}" ```