Releases: strimzi/strimzi-kafka-operator
Releases · strimzi/strimzi-kafka-operator
0.13.0
Main Changes
- Allow users to manually configure ACL rules (for example, using
kafka-acls.sh
) for special Kafka users*
andANONYMOUS
without them being deleted by the User Operator - Add support for configuring a Priority Class name for Pods deployed by Strimzi
- Add support for Kafka 2.3.0
- Add support for Kafka User resource status
- Add support for Kafka Connect resource status
- Add support for Kafka Connect S2I resource status
- Add support for Kafka Bridge resource status
- Add support for Kafka Mirror Maker resource status
- Add support for DNS annotations to
nodeport
type external listeners
Full list of changes can be found under the 0.13.0 milestone.
Upgrading from Strimzi 0.12.x
0.13.0 RC1
Main Changes
- Allow users to manually configure ACL rules (for example, using
kafka-acls.sh
) for special Kafka users*
andANONYMOUS
without them being deleted by the User Operator - Add support for configuring a Priority Class name for Pods deployed by Strimzi
- Add support for Kafka 2.3.0
- Add support for Kafka User resource status
- Add support for Kafka Connect resource status
- Add support for Kafka Connect S2I resource status
- Add support for Kafka Bridge resource status
- Add support for Kafka Mirror Maker resource status
- Add support for DNS annotations to
nodeport
type external listeners
Full list of changes can be found under the 0.13.0 milestone.
Upgrading from Strimzi 0.12.x
See the documentation for upgrade instructions.
0.12.2
0.12.1
0.12.0
0.12.0
- Drop support for Kubernetes 1.9 and 1.10 and OpenShift 3.9 and 3.10.
Versions supported since Strimzi 0.12.0 are Kubernetes 1.11 and higher and OpenShift 3.11 and higher.
This was required because the CRD versioning and CRD subresources support. - Added support for Kafka 2.2.1 and 2.1.1, dropped support for Kafka 2.0.0 and 2.0.1
- Persistent storage improvements
- Add resizing of persistent volumes
- Allow to specify different storage class for every broker
- Adding and removing volumes in Jbod Storage
- Custom Resources improvements
- New CRD version
v1beta1
. See documentation for more information about upgrading fromv1alpha1
tov1beta1
. - Log at the warn level when a custom resource uses deprecated or unknown properties
- Add initial support for the
status
sub-resource in theKafka
custom resource
- New CRD version
- Add support for Strimzi Kafka Bridge for HTTP protocol
- Reduce the number of container images needed to run Strimzi to just two:
kafka
andoperator
. - Add support for unprivileged users to install the operator with Helm
- Support experimental off-cluster access using Kubernetes Nginx Ingress
- Add ability to configure Image Pull Secrets for all pods in Cluster Operator
- Support for SASL PLAIN mechanism in Kafka Connect and Mirror Maker (for use with non-Strimzi Kafka cluster)
Upgrading from Strimzi 0.11.0
- Backup the existing Cluster Operator resources
- Update the Cluster Operator. You will need to modify the installation files according to the namespace the Cluster Operator is running in. For more information, see Strimzi documentation.
- If you modified one or more environment variables in your existing Cluster Operator Deployment, edit
install/cluster-operator/050-Deployment-cluster-operator.yaml to reflect the changes that you made. - When you have an updated configuration you can deploy it along with the rest of the install resources:
kubectl apply -f install/cluster-operator
- Wait for the associated rolling updates to complete.
- Update existing resources to the
v1beta1
API version and to cope with deprecated custom resource properties. For more information, see Strimzi documentation.
0.12.0-rc2
Changes since 0.12.0-rc1
- Throw error when a TLS KafkaUser with name >64 chars is created (#1698)
- Workaround the versioning issues in CRDs with KafkaStatus after version upgrade (#1695)
- Fix problems with certificate renewals caused by an incorrect commit (#1688)
- Update RBAC resources from
v1beta1
tov1
Upgrading from Strimzi 0.11.x
See the documentation - chapter 8. Strimzi and Kafka upgrades. Also notice the section 9. Strimzi resource upgrades about upgrading the resources from v1alpha1
to v1beta1
.
0.12.0-rc1
Main Changes
- Drop support for Kubernetes 1.9 and 1.10 and OpenShift 3.9 and 3.10. Versions supported since Strimzi 0.12.0 are Kubernetes 1.11 and higher and OpenShift 3.11 and higher. This was required because the CRD versioning and CRD sub-resources support.
- Added support for Kafka 2.2.0 and 2.1.1, dropped support for Kafka 2.0.0 and 2.0.1
- Persistent storage improvements
- Add resizing of persistent volumes
- Allow to specify different storage class for every broker
- Adding and removing volumes in Jbod Storage
- Custom Resources improvements
- New CRD version
v1beta1
. See documentation for more information about upgrading fromv1alpha1
tov1beta1
. - Log at the warn level when a custom resource uses deprecated or unknown properties
- Add initial support for the
status
sub-resource in theKafka
custom resource
- New CRD version
- Add support for Strimzi Kafka Bridge for HTTP protocol
- Reduce the number of container images needed to run Strimzi to just two:
kafka
andoperator
. - Add support for unprivileged users to install the operator with Helm
- Support experimental off-cluster access using Kubernetes Nginx Ingress
- Add ability to configure Image Pull Secrets for all pods in Cluster Operator
- Support for SASL PLAIN mechanism in Kafka Connect and Mirror Maker (for use with non-Strimzi Kafka cluster)
Full list of changes can be found under the 0.12.0 milestone.
Upgrading from Strimzi 0.11.x
See the documentation - chapter 8. Strimzi and Kafka upgrades. Also notice the section 9. Strimzi resource upgrades about upgrading the resources from v1alpha1
to v1beta1
.
0.11.4
0.11.3
Changes since 0.11.2:
- Resources configuration should be properly passed from MirrorMaker CR to the Deployment (#1494)
- Fix JMV options for Kafka Mirror Maker (#1570)
- Do not touch the secrets with CA which were created by the users (#1497)
- Support for SASL PLAIN authentication in Kafka Connect and Kafka Connect S2I (#1584)