-
Epic
-
Resolution: Done
-
Critical
-
None
-
None
-
None
-
Upgrade service to Kafka 3.2.x
-
False
-
False
-
No
-
To Do
-
MGDSRVS-336 - Keep Openshift Streams components up-to-date
-
0% To Do, 0% In Progress, 100% Done
-
---
-
---
WHAT
Upgrade RHOSAK from Managed Kafka 3.0.1 to 3.2.x. Strimzi 0.26 does not support Kafka 3.2.0, so MGDSTRM-8664 must be done first.
WHY
Maintain software currency.
HOW
- Review the https://dist.apache.org/repos/dist/release/kafka/3.2.0/RELEASE_NOTES.html against the assumptions we make already in about Kafka in the service. Things we want to think about (not exhaustive):
- Are there new configuration options?
- Are container resources used by fleetshard still good?
- Any changes to metrics? Any new metrics we should be configuring?
- Any changes to any extension points already used by Kafka (Authorizer, CreateTopicPolicy etc).
- Update pipeline and make bundle release
- Documentation will be published on the source https://source.redhat.com/communitiesatredhat/communities_of_practice/cross_cutting_co/cloud_services_cop/cloud_services/rhosak -> Current location: https://docs.google.com/document/d/1D9fnWRrnFGupifjr_0MdmrUBy703elYfVTmZcOVoRLc/edit#
- Upgrading existing instances to be managed by the new Kafka version.
DONE
- Kafka 3.2.0 available in the service
- Existing Kafka 3.0.1 instances upgraded to Kafka 3.2.0.
- blocks
-
-
- Closed
-
-
-
- Closed
-
-
MGDSTRM-8857 alterIsr request will not be retried after error returned in Kafka v3.0.1
-
- Closed
-
-
MGDSTRM-8910 Once service is upgraded to Kafka 3.2.0 update SOPs to remove workarounds for ISR updates failing
-
- Closed
-
- is blocked by
-
-
- Closed
-
- mentioned on
(8 mentioned on)
