helm/strimzi/strimzi-kafka-operator 0.10.0

on Artifact Hub

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-claim → strimzi.io/delete-claim
  • operator.strimzi.io/manual-rolling-update → strimzi.io/manual-rolling-update
  • operator.strimzi.io/delete-pod-and-pvc → strimzi.io/delete-pod-and-pvc
  • operator.strimzi.io/generation → strimzi.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.