Skip to content

Conversation

@sbernauer
Copy link
Member

@sbernauer sbernauer commented Dec 22, 2025

This is a small fixup of #1129
The changed CRD is only caused bycargo update (and not any other bump), so this is an entirely operator-rs internal change, as the operators themselves have their own Cargo lockfiles.
The actual change is a bugfix and comes from Arnavion/k8s-openapi#171.

To me the new CRD still looks valid (altough there is a needless {} in there), it successfully applied to a kind cluster.

I also ran cargo update -p k8s-openapi in zookeeper-op and the smoke tests passed

@sbernauer sbernauer self-assigned this Dec 22, 2025
@sbernauer sbernauer moved this to Development: Waiting for Review in Stackable Engineering Dec 22, 2025
@sbernauer sbernauer enabled auto-merge December 23, 2025 07:27
Copy link
Member

@Maleware Maleware left a comment

Choose a reason for hiding this comment

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

LGTM! The extra - {} is strange indeed but looks valid to me too

@sbernauer sbernauer added this pull request to the merge queue Dec 23, 2025
Merged via the queue into main with commit 612b8f4 Dec 23, 2025
5 checks passed
@sbernauer sbernauer deleted the fix/regenerate-crds branch December 23, 2025 08:13
@sbernauer sbernauer moved this from Development: Waiting for Review to Development: Done in Stackable Engineering Dec 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Development: Done

Development

Successfully merging this pull request may close these issues.

3 participants