Skip to content

test: Fix tests on k8s 1.35 by applying the TrinoCatalog after the TrinoCluster#857

Open
razvan wants to merge 3 commits intomainfrom
fix/854
Open

test: Fix tests on k8s 1.35 by applying the TrinoCatalog after the TrinoCluster#857
razvan wants to merge 3 commits intomainfrom
fix/854

Conversation

@razvan
Copy link
Member

@razvan razvan commented Mar 4, 2026

@razvan razvan self-assigned this Mar 4, 2026
@razvan razvan moved this to Development: Waiting for Review in Stackable Engineering Mar 4, 2026
@razvan razvan requested a review from a team March 4, 2026 12:05
Copy link
Member

@sbernauer sbernauer left a comment

Choose a reason for hiding this comment

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

I can totally see how this fixes the test, but sadly it's the easy way out. Many customer setups create the TrinoCatalogs after the TrinoCluster. It wound be a pity if they all run into this, researching the underlying k8s 1.35 problem would be great...

@sbernauer sbernauer changed the title fix: pod spec doesn't match sts spec test: Fix tests on k8s 1.35 by applying the TrinoCatalog after the TrinoCluster Mar 4, 2026
Co-authored-by: Sebastian Bernauer <sebastian.bernauer@stackable.de>
@razvan razvan requested a review from sbernauer March 4, 2026 16:33
@razvan razvan enabled auto-merge March 4, 2026 16:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Development: Waiting for Review

Development

Successfully merging this pull request may close these issues.

bug: pod spec doesn't match sts template spec

2 participants