Repository navigation
chore: Release stackable-operator 0.120.0, stackable-versioned 0.12.0 - #1297
Merged
Merged
Conversation
Member
|
note that we should also release stackable-versioned 0.12.0 please, as there has been changes as well. |
Techassi
requested changes
Oct 12, 2026
Techassi
left a comment
Member
There was a problem hiding this comment.
One comment, otherwise good to go.
sbernauer
previously approved these changes
Oct 12, 2026
Techassi
reviewed
Oct 12, 2026
Co-authored-by: Techassi <git@techassi.dev>
Techassi
approved these changes
Oct 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
stackable-operator 0.120.0
Added
crd::openlineagemodule with theOpenLineageConnectionCRD (#1250).Changed
SecurityContextBuilder::with_stackable_defaultssetsallowPrivilegeEscalation: falseandcapabilities.drop: [ALL], andPodSecurityContextBuilder::with_stackable_defaultsadditionallysets
seccompProfile.type: RuntimeDefault(#1292).Together these satisfy the
restrictedPod Security Standard, which plain Kubernetes enforcesonly if the namespace opts in and which OpenShift's SCCs inject during admission either way, so
the Pods OpenShift ends up running are unchanged.
And because OpenShift has already applied these for years we're pretty sure that this change is safe for us.
Operators already call
PodSecurityContextBuilder::with_stackable_defaults, so theseccompProfiledefault reaches their Pods with the dependency bump alone, nothing else to do.allowPrivilegeEscalationandcapabilitieshave no Pod-level equivalent, so a Pod is onlycovered once every one of its containers is built with
SecurityContextBuilder.stackable-versioned 0.12.0
Added
#[versioned(hint(map))]to provide a hint for map types during conversion (#1285).Fromimpl (#1284).