Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(downgrade): highlights the standard order of downgrade #11144

Merged
merged 3 commits into from
Feb 17, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 18 additions & 8 deletions documentation/assemblies/upgrading/assembly-downgrade.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -7,18 +7,28 @@

[role="_abstract"]
If you are encountering issues with the version of Strimzi you upgraded to,
you can revert your installation to the previous version.
you can revert to a previous version.

If you used the YAML installation files to install Strimzi, you can use the YAML installation files from the previous release to perform the downgrade procedures.
You can downgrade Strimzi by updating the Cluster Operator and the version of Kafka you are using.
Kafka version downgrades are performed by the Cluster Operator.
If you installed Strimzi using the YAML installation files, you can use the files from the previous release to perform the downgrade.

Downgrading Strimzi involves two key steps:

. Downgrading the Kafka cluster to a version supported by the target Cluster Operator (if required).
. Downgrading the Cluster Operator to the previous release.
PaulRMellor marked this conversation as resolved.
Show resolved Hide resolved

If downgrading through multiple versions, you may need to repeat these steps.

Always downgrade Kafka before the Cluster Operator to maintain compatibility.
Ensure that the Kafka version you downgrade to is supported by the target Cluster Operator.
The metadata version of the Kafka cluster must not be higher than the maximum version supported by the downgraded Kafka version.

WARNING: The following downgrade instructions are only suitable if you installed Strimzi using the installation files.
If you installed Strimzi using another method, like {OperatorHub}, downgrade may not be supported by that method unless specified in their documentation.
To ensure a successful downgrade process, it is essential to use a supported approach.
If you installed Strimzi using another method, such as {OperatorHub}, downgrade may not be supported by that method unless specified in its documentation.

//steps to downgrade Kafka
include::../../modules/upgrading/proc-downgrade-kafka-kraft.adoc[leveloffset=+1]

//steps to downgrade the operators
include::../../modules/upgrading/proc-downgrade-cluster-operator.adoc[leveloffset=+1]

//steps to downgrade Kafka
include::../../modules/upgrading/proc-downgrade-kafka-kraft.adoc[leveloffset=+1]

Original file line number Diff line number Diff line change
Expand Up @@ -5,9 +5,7 @@
[id='proc-downgrade-cluster-operator-{context}']
= Downgrading the Cluster Operator to a previous version

If you are encountering issues with Strimzi,
you can revert your installation.

[role="_abstract"]
This procedure describes how to downgrade a Cluster Operator deployment to a previous version.

NOTE: Kafka clusters managed by Strimzi always use node pools.
Expand Down
Loading