-
Epic
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
Strimzi 0.29
-
False
-
None
-
False
-
No
-
To Do
-
MGDSRVS-336 - Keep Openshift Streams components up-to-date
-
0% To Do, 0% In Progress, 100% Done
-
---
-
---
-
MK - Sprint 222
Upgrade RHOSAK to Strimzi 0.29.
WHAT
Upgrade the service from using from Strimzi 0.26 to Strimzi 0.29.
In Scope
- Upgrade to the latest Strimzi version bringing software currency and removing the current reliance of backports features/defect fixes.
Not in Scope
- Adopt the new features of Strimzi 0.29 (e.g. podsets) - this will be separate Epics.
- Increment Kafka/Zookeeper versions etc. Kafka 3.0.1 remains supported from (https://strimzi.io/docs/operators/0.29.0/deploying.html#assembly-upgrading-kafka-versions-str)
HOW
Review https://github.com/strimzi/strimzi-kafka-operator/blob/main/CHANGELOG.md and work out the changes the upgrade will cause in Managed Kafka.
- 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 Strimzi version.
Questions:
Any changes to Strimzi resource footprint?
DONE
- RHOSAK bundle produced including Strimzi 0.26 and Strimzi 0.29
- RHOSAK bundle released to production
- Existing kafka instances migrated to that they are managed by the Strimzi 0.29 rather than the Strimzi 0.26 one.
- No Kafka upgrade (kafka instances remain at 3.0.1)
- blocks
-
MGDSTRM-8673 Upgrade service from Kafka 3.0.x to 3.2.x
- Closed
-
MGDSTRM-8746 Migration to StrimziPodSets
- Closed
- is duplicated by
-
MGDSTRM-9082 Upgrade Strimzi Operator to 0.29 version in RHOSAK
- Closed
- is related to
-
MGDSTRM-9261 StrimziKafkaStuck alert triggered by running out of space in /tmp
- Closed