-
Notifications
You must be signed in to change notification settings - Fork 218
feat: integration test for cross reference dependent resource #1203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@metacosm first I wanted this just to reproduce the issue, but probably won't hurt to merge it to main. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm ambivalent on whether to add this test or not, actually. We could retool it for performance testing or maybe only run it in some cases like once a day or something so that we don't always run rather intensive tests.
...operatorsdk/operator/sample/dependentresourcecrossref/DependentResourceCrossRefResource.java
Outdated
Show resolved
Hide resolved
…ample/dependentresourcecrossref/DependentResourceCrossRefResource.java Co-authored-by: Chris Laprun <[email protected]>
Maybe we could have it less intensive. Like not 500 but just 50. ( TBH not sure if that causes lot's of overhead. Actually it runs very fast already and k8s api should handle such load without any issues. But I probably would merge it with reducted number). |
…or-sdk/java-operator-sdk into concurrency-issue-dependents
Kudos, SonarCloud Quality Gate passed!
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
No description provided.