You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/ROOT/pages/release-notes.adoc
+23-4Lines changed: 23 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -245,14 +245,33 @@ Of the changes mentioned above, the following are breaking (or could lead to bre
245
245
246
246
==== Kafka operator
247
247
248
-
* Existing services will be migrated to the new format. Clients will need to re-read settings from the discovery configmap.
249
-
* Kafka is now only accessible from within the Kubernetes cluster by default. Set listener classes manually to expose it to the outside world (again).
250
-
* To complete an upgrade to this kafka-operator, all existing Kafka StatefulSets must be deleted manually. This will cause some downtime.
248
+
* Existing Kafka clusters will need to be migrated to using the Listener Operator.
249
+
Kafka clients will need to re-read settings from the discovery configmap (restart required).
250
+
Existing Kafka StatefulSets must be deleted manually. This will cause some downtime.
251
+
* Kafka is now only accessible from within the Kubernetes cluster by default.
251
252
252
253
.Breaking changes details
253
254
[%collapsible]
254
255
====
255
-
* `spec.blah`: Describe a change.
256
+
Migrating Kafka clusters to use the Listener Operator is done by deleting the Kafka StatefulSet after the new Stackable Operator for Kafka has been installed, by running the following:
Please note that this upgrade will randomize the address that users will have to connect to, so any external clients must re-read it from the discovery configuration after the upgrade has been completed.
0 commit comments