Skip to content

Releases: lsst-sqre/strimzi-registry-operator

0.7.1

30 Sep 13:41

Choose a tag to compare

This release publishes a multi-platform image (amd64 + arm64).

What's Changed

New Contributors

Full Changelog: 0.7.0...0.7.1

0.7.0

21 Aug 18:31

Choose a tag to compare

This release adds significant improvements to the Strimzi Registry Operator:

  • Modernize the operator codebase, adopt uv-based Python workflow with pyproject.toml, refresh dependencies, update GitHub Actions, and improve typing/formatting.
  • Update minikube workflow; test fixtures and docs refreshed.
  • Update RBAC for newer Kopf behavior and grant cluster-wide list of namespaces and watch CRDs.
  • Support for configuring Schema Registry topic name and the number of deployment replicas via StrimziSchemaRegistry CR.
  • Proper handling of spec.compatibilityLevel setting.
  • The Kafka cluster name is now read from the strimzi.io/cluster label on the StrimziSchemaRegistry CR.
    Breaking change: this label is now required.
  • Default Schema Registry image tag updated to 8.0.0.
  • Deprecated strimzi-version field replaced with strimziVersion.
  • Operator now correctly recreates the JKS secret when Kafka CA or client certs rotate.
  • Expanded documentation covering access the Schema Registry API after deployment, new configuration options and improved the installation instructions.

What's Changed

  • [neophile] Update dependencies by @sqrbot in #66
  • Bump python from 3.10.5-slim-bullseye to 3.10.6-slim-bullseye by @dependabot[bot] in #67
  • [neophile] Update dependencies by @sqrbot in #69
  • [neophile] Update dependencies by @sqrbot in #71
  • [neophile] Update dependencies by @sqrbot in #72
  • [neophile] Update dependencies by @sqrbot in #73
  • Bump python from 3.10.6-slim-bullseye to 3.10.7-slim-bullseye by @dependabot[bot] in #74
  • [neophile] Update dependencies by @sqrbot in #75
  • [neophile] Update dependencies by @sqrbot in #76
  • [neophile] Update dependencies by @sqrbot in #78
  • [neophile] Update dependencies by @sqrbot in #80
  • Update README.md by @mike-serchenia in #89
  • [DM-52032] Refresh schema-registry-operator codebase by @afausti in #109
  • Bump python from 3.13.5-slim-bookworm to 3.13.6-slim-bookworm by @dependabot[bot] in #110
  • Update operation block for deprecation by @medoror-mo in #103
  • [DM-52149] strimzi-registry-operator does not recreate the JKS secret by @afausti in #112
  • Bump actions/checkout from 4 to 5 by @dependabot[bot] in #114
  • Bump python from 3.13.6-slim-bookworm to 3.13.7-slim-bookworm by @dependabot[bot] in #115
  • [DM-52124] Support additional configuration in the strimzi-registry-operator by @afausti in #111
  • [DM-52192] Improve strimzi-registry-operator documentation by @afausti in #113
  • [DM-52227] Improve installation instructions by @afausti in #116

New Contributors

Full Changelog: 0.6.0...0.7.0

0.6.0

03 Aug 15:31
d59c3fc

Choose a tag to compare

Strimzi Registry Operator now adds the recommended Kubernetes labels to the Deployment and Service resources for the Confluent Schema Registry deployment.

What's Changed

Full Changelog: 0.5.0...0.6.0

0.5.0

29 Jul 16:29
9009b01

Choose a tag to compare

This release adds significant improvements for compatibility with newer versions of Strimzi and the Confluent Schema Registry.
The StrimziSchemaRegistry CRD has new and revised fields, which you should review before deploying this version:

  • The spec.listener field in StrimziSchemaRegistry now refers to the name of the of the listener — the spec.kafka.listeners[].name field of Strimzi's Kafka resource (with the kafka.strimzi.io/v1beta2 Strimzi API).
    With older versions of strimzi (API version kafka.strimzi.io/v1beta1), this refers to the type, which also doubled as a name in the spec.kafka.listeners.type or .external or .plain.
  • The Schema Registry's security protocol (kafkastore.security.protocol) is now configurable through the spec.securityProtocol of the StrimziSchemaRegistry resource. Default is SSL, but can be changed for plain text or SASL users.
  • The default subject compatibility level in the Schema Registry (schema.compatibility.level) can be set with the spec.compatibilityLevel field of StrimziSchemaRegistry. Details, as from previous versions of Strimzi Registry Operator, is forward`.
  • The Schema Registry Docker image is now configurable via registryImage and registryImageTag fields of StrimziSchemaRegistry. The defaults are updated to Schema Registry 7.2.1.
  • You can now set CPU and memeory requests and limits for the Schema Registry through the StrimziSchemaRegistry.

The default container registry for Strimzi Registry Operator is now ghcr.io (GitHub Container Registry): ghcr.io/lsst-sqre/strimzi-registry-operator.

What's Changed

New Contributors

Full Changelog: 0.4.1...0.5.0

0.5.0rc1

28 Jul 16:49
9028177

Choose a tag to compare

0.5.0rc1 Pre-release
Pre-release

This release adds significant improvements for compatibility with newer versions of Strimzi and the Confluent Schema Registry. The StrimziSchemaRegistry CRD has new and revised fields, which you should review before deploying this version:

  • The spec.listener field in StrimziSchemaRegistry now refers to the name of the of the listener — the spec.kafka.listeners[].name field of Strimzi's Kafka resource (with the kafka.strimzi.io/v1beta2 Strimzi API). With older versions of strimzi (API version kafka.strimzi.io/v1beta1), this refers to the type, which also doubled as a name in the spec.kafka.listeners.type or .external or .plain.
  • The Schema Registry's security protocol (kafkastore.security.protocol) is now configurable through the spec.securityProtocol of the StrimziSchemaRegistry resource. Default is SSL, but can be changed for plain text or SASL users.
  • The default subject compatibility level in the Schema Registry (schema.compatibility.level) can be set with the spec.compatibilityLevel field of StrimziSchemaRegistry. Details, as from previous versions of Strimzi Registry Operator, is forward`.
  • The Schema Registry Docker image is now configurable via registryImage and registryImageTag fields of StrimziSchemaRegistry. The defaults are updated to Schema Registry 7.2.1.
  • You can now set CPU and memeory requests and limits for the Schema Registry through the StrimziSchemaRegistry.

The default container registry for Strimzi Registry Operator is now ghcr.io (GitHub Container Registry): ghcr.io/lsst-sqre/strimzi-registry-operator.

What's Changed

New Contributors

Full Changelog: 0.4.1...0.5.0rc1

0.4.1

20 Jan 20:35
14d682a

Choose a tag to compare

What's Changed

Full Changelog: 0.4.0...0.4.1

0.4.0

20 Jan 20:20
8d09169

Choose a tag to compare

What's Changed

Full Changelog: 0.3.0...0.4.0