Skip to content

Limit aggregated conditions to fit into API limits #2443

Open
@mflendrich

Description

@mflendrich

Issue originally authored by tnozicka as #1075

Is this a bug report or feature request?

  • Feature Request

What should the feature do:
#1070 introduced aggregated conditions that can possibly overflow max size for reason and messages fields. We should add some smart function that trips it while maintaining the most important information and and makes sure to mark the content as stripped.

Note: If we hit those limits today the update status fails and the observe generation won't match so we don't get a false positive and the error data will usually eventually scale down to fit those limits but we should do our best to propagate status at any point.

Metadata

Metadata

Assignees

No one assigned

    Labels

    good-first-issueIssue that is good as an onboarding task for newcomerskind/bugCategorizes issue or PR as related to a bug.lifecycle/from-migrationIndicates that this issue is a copy of a corresponding issue mentioned in the description.priority/backlogHigher priority than priority/awaiting-more-evidence.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions