Skip to content

@scholzj scholzj released this Mar 5, 2019 · 84 commits to master since this release

Assorted bug-fixes:

  • OpenShift detection on OpenShfit 4.0 (#1405)
  • Zookeeper leader selection during certificate renewal (#1404)
  • Fix network policies between CO and Zookeeper (#1402)
  • Fix several NPE exceptions (#1399, #1386)
  • Fix RBAC issue when User Operator is listening to different namespace (#1391)
  • Fix problem with upgrade form 0.8.x (#1397)
  • Fix regular rolling updates outside of maintenance windows (#1398)

Minor improvements:

  • Improve log message for unsupported Kafka versions (#1394)
Assets 8

@scholzj scholzj released this Feb 25, 2019 · 84 commits to master since this release

Main changes:

  • Add support for JBOD storage for Kafka brokers
  • Allow users to configure the default ImagePullPolicy
  • Sample Prometheus alerts
  • More configuration options for off cluster access
    • Configure advertised hosts and ports
    • Configure NodePort numbers
    • Configure hosts OpenShift routes
    • Add additional DNS name for bootstrap service
  • Support for watching all namespaces
  • Operator Lifecycle Manager integration

Full list of changes can be found under the 0.11.0 milestone.


Upgrading from Strimzi 0.10.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 cope with deprecated custom resource properties.
    • If you have Kafka resources that specify Kafka.spec.topicOperator, rewrite them to use Kafka.spec.entityOperator.topicOperator instead.
Assets 8
Pre-release

@scholzj scholzj released this Feb 22, 2019 · 84 commits to master since this release

Changes since RC1

  • Fixes to YAML files
  • Documentation updates
  • Minor improvements to watching of all namespaces

Upgrading from Strimzi 0.10.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 cope with deprecated custom resource properties.
    • If you have Kafka resources that specify Kafka.spec.topicOperator, rewrite them to use Kafka.spec.entityOperator.topicOperator instead.
Assets 8
Pre-release

@scholzj scholzj released this Feb 21, 2019 · 84 commits to master since this release

Main changes:

  • Add support for JBOD storage for Kafka brokers
  • Allow users to configure the default ImagePullPolicy
  • Sample Prometheus alerts
  • More configuration options for off cluster access
    • Configure advertised hosts and ports
    • Configure NodePort numbers
    • Configure hosts OpenShift routes
    • Add additional DNS name for bootstrap service
  • Support for watching all namespaces
  • Operator Lifecycle Manager integration

Full list of changes can be found under the 0.11.0 milestone.


Upgrading from Strimzi 0.10.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 cope with deprecated custom resource properties.
    • If you have Kafka resources that specify Kafka.spec.topicOperator, rewrite them to use Kafka.spec.entityOperator.topicOperator instead.
Assets 8

@scholzj scholzj released this Feb 4, 2019 · 176 commits to master since this release

Main changes:

  • Support for Kafka 2.1.0
  • Support for Kafka upgrades
  • Add health-checks to TLS sidecars
  • Add support for new fields in the Pod template: terminationGracePeriod, securityContext and imagePullSecrets
  • Rename annotations to use the strimzi.io domain consistently (The old annotations are deprecated, but still functional):
    • cluster.operator.strimzi.io/delete-claimstrimzi.io/delete-claim
    • operator.strimzi.io/manual-rolling-updatestrimzi.io/manual-rolling-update
    • operator.strimzi.io/delete-pod-and-pvcstrimzi.io/delete-pod-and-pvc
    • operator.strimzi.io/generationstrimzi.io/generation
  • Add support for mounting Secrets and Config Maps into Kafka Connect and Kafka Connect S2I
  • Add support for NetworkPolicy peers in listener configurations
  • Make sure the TLS sidecar pods shutdown only after the main container
  • Add support for Pod Disruption Budgets

Full list of changes can be found under the 0.10.0 milestone.


Upgrading from Strimzi 0.9.0

  • Update your existing Kafka, KafkaConnect, KafkaConnectS2I, and KafkaMirrorMaker resources, as follows:
    • Add Kafka.spec.kafka.version with the value 2.0.1
    • Add KafkaConnect.spec.version with the value 2.0.1
    • Add KafkaConnectS2I.spec.version with the value 2.0.1
    • Add KafkaMirrorMaker.spec.version with the value 2.0.1
  • Wait for the associated rolling updates to complete.
  • Backup the existing Cluster Operator resources:
kubectl get -l app=strimzi > strimzi-backup.yaml
  • 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 cope with deprecated custom resource properties.
    • If you have Kafka resources that specify Kafka.spec.topicOperator, rewrite them to use Kafka.spec.entityOperator.topicOperator instead.
Assets 8
Pre-release

@scholzj scholzj released this Jan 30, 2019 · 176 commits to master since this release

Main changes since RC1

  • Update sundr.io and some related test to make sure build is working in all environments
  • Merged Strimzi and Kafka upgrade documentation

Upgrading from Strimzi 0.9.0

See 0.10.0 RC1 or the documentation for the upgrade procedure.

Assets 8
Pre-release

@scholzj scholzj released this Jan 28, 2019 · 176 commits to master since this release

Main changes:

  • Support for Kafka 2.1.0
  • Support for Kafka upgrades
  • Add health-checks to TLS sidecars
  • Add support for new fields in the Pod template: terminationGracePeriod, securityContext and imagePullSecrets
  • Rename annotations to use the strimzi.io domain consistently (The old annotations are deprecated, but still functional):
    • cluster.operator.strimzi.io/delete-claimstrimzi.io/delete-claim
    • operator.strimzi.io/manual-rolling-updatestrimzi.io/manual-rolling-update
    • operator.strimzi.io/delete-pod-and-pvcstrimzi.io/delete-pod-and-pvc
    • operator.strimzi.io/generationstrimzi.io/generation
  • Add support for mounting Secrets and Config Maps into Kafka Connect and Kafka Connect S2I
  • Add support for NetworkPolicy peers in listener configurations
  • Make sure the TLS sidecar pods shutdown only after the main container
  • Add support for Pod Disruption Budgets

Full list of changes can be found under the 0.10.0 milestone.


Upgrading from Strimzi 0.9.0

  • Update your existing Kafka, KafkaConnect, KafkaConnectS2I, and KafkaMirrorMaker resources, as follows:
    • Add Kafka.spec.kafka.version with the value 2.0.1
    • Add KafkaConnect.spec.version with the value 2.0.1
    • Add KafkaConnectS2I.spec.version with the value 2.0.1
    • Add KafkaMirrorMaker.spec.version with the value 2.0.1
  • Wait for the associated rolling updates to complete.
  • Backup the existing Cluster Operator resources:
kubectl get -l app=strimzi > strimzi-backup.yaml
  • 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 cope with deprecated custom resource properties.
    • If you have Kafka resources that specify Kafka.spec.topicOperator, rewrite them to use Kafka.spec.entityOperator.topicOperator instead.
Assets 8

@scholzj scholzj released this Dec 13, 2018 · 254 commits to master since this release

Main changes:

  • Add possibility to label and annotate different resources (#1039)
  • Add support for TransactionalID in KafkaUser resource
  • Update to Kafka 2.0.1
  • Add maintenance time windows support for allowing CA certificates renewal rolling update started only in specific times (#1117)

Full list of changes can be found under the 0.9.0 milestone.

Assets 8
Pre-release

@scholzj scholzj released this Dec 10, 2018 · 254 commits to master since this release

Main changes:

  • Add possibility to label and annotate different resources (#1093)
  • Add support for TransactionalID in KafkaUser resource
  • Update to Kafka 2.0.1
  • Add maintenance time windows support for allowing CA certificates renewal rolling update started only in specific times (#1117)

Full list of changes can be found under the 0.9.0 milestone.

Assets 8
You can’t perform that action at this time.