Skip to content

tracking: Release Notes for SDP 26.11.0 - #987

Draft
Techassi wants to merge 9 commits into
mainfrom
docs/release-notes-26.11.0
Draft

Techassi wants to merge 9 commits into
mainfrom
docs/release-notes-26.11.0

Conversation

@Techassi

@Techassi Techassi commented Nov 18, 2026 •

Copy link
Copy Markdown
Member

Release Notes for SDP 26.11.0

Part of stackabletech/issues#889.

Caution

Please assign the applicable scheduled-for/26.11.0 label.

Tip

  • Use the commented out template headings in release-notes.
  • Begin each sentence on a new line. This helps with review suggestions and diffing.
  • Use xrefs for links to other parts of the documentation so that they remain valid across versions.

Release note compilation tasks

  • Check Issues for Product and Platform release notes
  • Check PRs for Product and Platform release notes
  • Optionally check the Changelogs in case release notes were missed
  • Compile list of release highlights
  • Upgrade guide: Document how to use stackablectl to uninstall all and install new release
  • Upgrade guide: Document how to use helm to uninstall all and install new release
  • Upgrade guide: Every breaking change of all our operators
  • Upgrade guide: List removed product versions (if there are any)
  • Upgrade guide: List removed operators (if there are any)
  • Upgrade guide: List supported Kubernetes versions

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

  • Check overall document structure
  • Check spelling, grammar, and correct wording
  • Check that internal links are xrefs
  • Check that rendered links are valid
  • Check that each sentence begins on a new line

@netlify

netlify Bot commented Nov 18, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for stackable-docs ready!

Name Link
🔨 Latest commit 82f4bd7
🔍 Latest deploy log https://app.netlify.com/projects/stackable-docs/deploys/6b001c894acfc7a380f8bd76
😎 Deploy Preview https://deploy-preview-987--stackable-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@Techassi Techassi moved this to Development: In Progress in Stackable Engineering Nov 18, 2026
This class can be used to highlight the "Breaking" keyword, for
example in the release notes.

@adwk67 adwk67 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just some typos.


===== Open Policy Agent

Products have a soft default affinity to OPA server pods now, favouring local routing to a available OPA pod.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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].

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Removed ib https://github.com/stackabletech/actions/pull/123[actions#123].
Removed in https://github.com/stackabletech/actions/pull/123[actions#123].

@razvan razvan left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

my ideas

Comment on lines +9 to +10
* 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

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Suggested change
* 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

Comment on lines +44 to +48
* 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].

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A warning is not a new platform feature. Maybe move it to fixes?

==== New platform features

===== General

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
====== 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

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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:**

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Suggested change
[.breaking-keyword]**Breaking:**
[.breaking-keyword]**Breaking**

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Development: In Progress

Development

Successfully merging this pull request may close these issues.

3 participants