chore: Release stackable-operator 0.115.0 - #1258
Merged
Merged
Conversation
siegfriedweber
self-requested a review
August 4, 2026 13:41
siegfriedweber
moved this from Development: Waiting for Review
to Development: In Review
in Stackable Engineering
siegfriedweber
left a comment
siegfriedweber
left a comment
Member
There was a problem hiding this comment.
Does your change in https://github.com/stackabletech/operator-rs/pull/1257/changes#diff-bc7736d26396b13b125507bb70f16bb26bfcefab22b1203338ab7e2092821ecf also require a stackable-versioned release?
Member
Author
|
I'd say no, as it's a purely internal change. IMO we only need to call out bumps to re-exported crates (kube, k8s-openapi), as they are technically breaking. |
Techassi
moved this from Development: In Review
to Development: Done
in Stackable Engineering
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
4 participants
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.
Changed
PodSecurityContextBuilder::newwas removed in favor ofPodSecurityContextBuilder::with_stackable_defaults(same for
SecurityContextBuilder) (#1205).This function already sets up some defaults we want to use across the platform.
Currently this is
runAsNonRoot: trueforPodSecurityContextBuilder, which might cause product Pods to crash and require changes.PodSecurityContextBuilder::run_as_non_rootnow takes aboolinstead of assuming consumers always want to set it totrue(#1205).This is needed to allow users setting it to
falsein case the newwith_stackable_defaultsfunction sets it totrue.SecurityContextBuilder::run_as_roothas been removed (#1205).kubeto4.2.0(#1257).additionalPrinterColumns,categoriesandshortNameswhere always included in the CRD, which lead to ArgoCD thinking the CRs where out of sync.