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(kraft): adds a procedure for zookeeper to kraft migration #9633

Merged
merged 16 commits into from Mar 2, 2024

Conversation

PaulRMellor
Copy link
Contributor

@PaulRMellor PaulRMellor commented Feb 2, 2024

Documentation

Adds a new procedure that describes how to migrate from ZooKeeper-based to KRaft-based Kafka cluster.
Also includes steps to roll back, if required.

Checklist

Please go through this checklist and make sure all applicable tasks have been done

  • Write tests
  • Make sure all tests pass
  • Update documentation
  • Check RBAC rights for Kubernetes / OpenShift roles
  • Try your changes from Pod inside your Kubernetes and OpenShift cluster, not just locally
  • Reference relevant issue(s) and close them after merging
  • Update CHANGELOG.md
  • Supply screenshots for visual changes, such as Grafana dashboards

Signed-off-by: prmellor <pmellor@redhat.com>
@PaulRMellor PaulRMellor added this to the 0.40.0 milestone Feb 2, 2024
@PaulRMellor PaulRMellor self-assigned this Feb 2, 2024
Signed-off-by: prmellor <pmellor@redhat.com>
PaulRMellor and others added 3 commits February 5, 2024 12:22
Signed-off-by: prmellor <pmellor@redhat.com>
Signed-off-by: prmellor <pmellor@redhat.com>
Signed-off-by: PaulRMellor <47596553+PaulRMellor@users.noreply.github.com>
@ppatierno
Copy link
Member

@PaulRMellor I added the "do-not-merge" label because this one should anyway wait for the implementation in #9480 being merged as well.

Signed-off-by: prmellor <pmellor@redhat.com>
Copy link
Member

@scholzj scholzj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. But it shoud be approved by Paolo as the migration SME.

Copy link
Member

@see-quick see-quick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

first iteration adding a few comments, I would also do the second one to check all procedures you have add here.

Signed-off-by: prmellor <pmellor@redhat.com>
Signed-off-by: prmellor <pmellor@redhat.com>
Signed-off-by: prmellor <pmellor@redhat.com>
Signed-off-by: prmellor <pmellor@redhat.com>
Copy link
Member

@ppatierno ppatierno left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thanks!
As already said we'll not merge this until the corresponding implementation PR #9480 is merged as well.

Copy link
Contributor

@fvaleri fvaleri left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks. Left some comments.

@ppatierno
Copy link
Member

@PaulRMellor while having an offline chat with @fvaleri it could be worth mentioning that if your initial configuration has the inter broker protocol and/or log message format set, you should remove them at the end of the migration. The brokers and controllers will be rolled one more time to update them.
At the same time even when removing the spec.zookeeper.
There are warnings in the Kafka CR but after the rolling, those are removed.

Copy link
Member

@see-quick see-quick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a few comments from me 👍 Looks good

Signed-off-by: prmellor <pmellor@redhat.com>
Copy link
Member

@ppatierno ppatierno left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@PaulRMellor We should take all the updates not related to migration out of this PR but having a new one for them. I see you updated annotation values in all other places, but I would move them for a new PR. Let's take this PR for migration only.

Signed-off-by: prmellor <pmellor@redhat.com>
@PaulRMellor PaulRMellor force-pushed the docs_kraft-migration branch 2 times, most recently from 8c7f5e9 to 2d80e20 Compare February 9, 2024 14:35
Signed-off-by: prmellor <pmellor@redhat.com>
Signed-off-by: prmellor <pmellor@redhat.com>
Copy link
Member

@ppatierno ppatierno left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Back to green!

Copy link
Contributor

@fvaleri fvaleri left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks.

@ppatierno
Copy link
Member

@PaulRMellor while having an offline chat with @fvaleri it could be worth mentioning that if your initial configuration has the inter broker protocol and/or log message format set, you should remove them at the end of the migration. The brokers and controllers will be rolled one more time to update them.
At the same time even when removing the spec.zookeeper.
There are warnings in the Kafka CR but after the rolling, those are removed.

@PaulRMellor I don't see addressed the above comment here.

Signed-off-by: prmellor <pmellor@redhat.com>
@ppatierno ppatierno mentioned this pull request Feb 22, 2024
5 tasks
Signed-off-by: prmellor <pmellor@redhat.com>
@ppatierno ppatierno merged commit e266f0a into strimzi:main Mar 2, 2024
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants