test: add max CRD size check, add version probe job retries - #305
Merged
Conversation
|
Docs PR opened: ClickHouse/ClickHouse#116384 Synced two Kubernetes operator doc pages from upstream, adding cluster-level NetworkPolicy guide content and matching API reference entries. |
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
1 participant
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.
Why
CRD size grows fast and we need to detect when it grows close to k8s 1mb limit.
E2E test runners have restricted resources which sometimes results in the failed probe jobs, which block the tests as they are not retried.
What