Limit provider error response to 1000 characters #38
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.
This PR limits error response that is sent to kubernetes, to the first 1000 characters.
Context:
App platform received resource exhausted alert on flipop :
ResourceExhausted error (desc = trying to send message larger than max (2361634 vs. 2097152)) in the flipop pod (5 restarts in 30h).flipop updates the status message in the floatingippool resource when it encounters an error. That message includes the response it got back from the API. When Cloud Control Panel / API is down (see inci-1955), we display a big html file containing an image.
Which made the response size > 2MB , which is gRPC's default.
https://logs.internal.digitalocean.com/goto/f4a59480-f483-11ef-9702-c10ab0923a22