Use default timeout for listing CRDs #235
Merged
Conversation
This file contains 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
ParthaI
approved these changes
Jun 26, 2024
misraved
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Plugin Version: 0.28.0
Problem
Listing Custom Resource Definitions (CRDs) fails on large clusters.
Investigation
On a large cluster with over 2000 CRDs, we observed that the command
.inspect kubernetesdid not create tables for custom resource definitions. While all other tables were created successfully, CRD tables were missing.No errors were found in the logs, so we modified the code to print the error at this location. This revealed that there was a silent timeout during the listing of custom resources, with no error logs or codes returned.
Fix