-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Update the Kafka recovery procedure with KRaft notes #10728
Conversation
This patch should close strimzi#10722. Signed-off-by: Federico Valeri <fedevaleri@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added a nit. But LGTM otherwise. Thanks for looking into it.
I wonder if it would be easier to have just a second procedure for KRaft only instead of mixing it. It would be easier to just delete one in few months when Zoo is removed.
documentation/modules/managing/proc-cluster-recovery-volume.adoc
Outdated
Show resolved
Hide resolved
Signed-off-by: Federico Valeri <fedevaleri@gmail.com>
At the moment Kraft commands are just limited to this point, but if you prefer to have a second procedure I can do that. |
Let's leave it to @PaulRMellor I guess. The advantage of separate procedures would be that we just ned to drop one once ZooKeeper is removed. That is it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks,
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @fvaleri
I left a few comments, mainly about the level of detail we might want to include for someone following the steps.
I agree with Jakub that it might be easier to have two procedures
documentation/modules/managing/proc-cluster-recovery-volume.adoc
Outdated
Show resolved
Hide resolved
documentation/modules/managing/proc-cluster-recovery-volume.adoc
Outdated
Show resolved
Hide resolved
documentation/modules/managing/proc-cluster-recovery-volume.adoc
Outdated
Show resolved
Hide resolved
documentation/modules/managing/proc-cluster-recovery-volume.adoc
Outdated
Show resolved
Hide resolved
documentation/modules/managing/proc-cluster-recovery-volume.adoc
Outdated
Show resolved
Hide resolved
Signed-off-by: Federico Valeri <fedevaleri@gmail.com>
@PaulRMellor @scholzj better? I also need to update the pod listing in a separate commit. |
Signed-off-by: Federico Valeri <fedevaleri@gmail.com>
documentation/modules/managing/proc-cluster-recovery-volume.adoc
Outdated
Show resolved
Hide resolved
Signed-off-by: Federico Valeri <fedevaleri@gmail.com>
Signed-off-by: Federico Valeri <fedevaleri@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
New procedure looks good.
I think we don't need the sub-steps now.
documentation/modules/managing/proc-cluster-recovery-volume-zk.adoc
Outdated
Show resolved
Hide resolved
documentation/modules/managing/proc-cluster-recovery-volume.adoc
Outdated
Show resolved
Hide resolved
documentation/modules/managing/proc-cluster-recovery-volume.adoc
Outdated
Show resolved
Hide resolved
documentation/modules/managing/proc-cluster-recovery-volume.adoc
Outdated
Show resolved
Hide resolved
Signed-off-by: Federico Valeri <fedevaleri@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Fede 👍
Type of change
Description
This patch should close #10722.
The challenging task here is to retrieve the
clusterId
from existing volumes.I thought to spin up a temporary pod for that, ugly but works.
Let me know if you have a better idea.
Checklist