Repository navigation
Conversation
✅ Deploy Preview for stackable-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This class can be used to highlight the "Breaking" keyword, for example in the release notes.
|
|
||
| ===== Open Policy Agent | ||
|
|
||
| Products have a soft default affinity to OPA server pods now, favouring local routing to a available OPA pod. |
There was a problem hiding this comment.
| Products have a soft default affinity to OPA server pods now, favouring local routing to a available OPA pod. | |
| Products have a soft default affinity to OPA server pods now, favouring local routing to an available OPA pod. |
| With this release we are removing SLSA provenance attestations for our images and charts for now, because it caused problems for us. | ||
| We will try to add SLSA provenance attestations again in a future release. | ||
| + | ||
| Removed ib https://github.com/stackabletech/actions/pull/123[actions#123]. |
There was a problem hiding this comment.
| Removed ib https://github.com/stackabletech/actions/pull/123[actions#123]. | |
| Removed in https://github.com/stackabletech/actions/pull/123[actions#123]. |
| * link:#kafka-new-features-26_11_0[Apache Kafka]: The controller StatefulSets must be recreated when upgrading | ||
| * link:#label-improvements-26_11_0[Various operators]: StatefulSets maintained by various operators need re-creation because of label changes |
There was a problem hiding this comment.
There is no need to single out Kafka in here. The net effect for users is the same (they need to restart the STSs) even if the cause is different. This is documented in detail later in this doc.
| * link:#kafka-new-features-26_11_0[Apache Kafka]: The controller StatefulSets must be recreated when upgrading | |
| * link:#label-improvements-26_11_0[Various operators]: StatefulSets maintained by various operators need re-creation because of label changes | |
| * link:#label-improvements-26_11_0[Various operators]: StatefulSets maintained by various operators need re-creation because of label changes |
| * A warning is now logged when a defined object override was not applied. | ||
| This happens most often when the override does not define the namespace of the object. | ||
| Previously, this was difficult to debug. | ||
| + | ||
| Implemented in https://github.com/stackabletech/operator-rs/pull/1264[operator-rs#1264]. |
There was a problem hiding this comment.
A warning is not a new platform feature. Maybe move it to fixes?
| ==== New platform features | ||
|
|
||
| ===== General | ||
|
|
There was a problem hiding this comment.
| ====== OpenLineage | |
| https://openlineage.io/[OpenLineage] is an open standard for collecting data lineage: which jobs ran, which datasets they read, and which datasets they wrote. | |
| Products emit OpenLineage events while they work and send them to an OpenLineage-compatible backend, such as https://marquezproject.ai/[Marquez] or https://docs.datahub.com/docs/lineage/openlineage[DataHub]. | |
| The back-end stitches the events from all producers into one lineage graph, so you can answer questions such as "where does this table come from?" or "what breaks if I change this column?". | |
| This release adds a unified way to manage OpenLineage configurations across products. | |
| The Airflow, Trino and Spark operators provide support HTTPS back-ends including authentication. |
|
|
||
| [#kafka-new-features-26_11_0] | ||
| ===== Apache Kafka | ||
|
|
There was a problem hiding this comment.
| Operator support for Kraft has been almost completely rewritten in this release and we are confident that we can remove the `experimental` label attached to it. | |
| KRaft based installations are now much more robust and secure. | |
| Controller scaling is now much more reliable and has almost no impact on broker activity. | |
| Security wise, controllers use the same internal security mechanisms as the brokers regardless of the client facing protocols. | |
| Administrative operations are now subject to the same authorization policies as topic and data management operations. |
| Controllers are scaled one at a time, because KRaft only processes one voter change at a time. | ||
| + | ||
| -- | ||
| [.breaking-keyword]**Breaking:** |
There was a problem hiding this comment.
I would remove the colon in all these call-outs. They are inconsistent with other call-outs in previous release notes, not to mention visually awkward.
| [.breaking-keyword]**Breaking:** | |
| [.breaking-keyword]**Breaking** |
Release Notes for SDP 26.11.0
Part of stackabletech/issues#889.
Caution
Please assign the applicable
scheduled-for/26.11.0label.Tip
Release note compilation tasks
Optionally check the Changelogs in case release notes were missedUpgrade guide: List removed operators (if there are any)Each of the following tasks focuses on a specific goal and should be done once the items above have been completed.
Release note review tasks