Skip to content

Test status updates in longevity test #1125

Open
@pleshakov

Description

@pleshakov

In longevity testing for 1.0.0 #1113 , control plane transactions weren't fully tested. While we tested that NGF processes EndpointSlices changes, we didn't test any transaction that result into status of updates of resources, like a change in an HTTPRoute.

Status updates are important, because they tell users (human or CI/CD) the status of a resource -- in general, success or failure. Without that, users can't be confident.

Acceptance criteria:

  • Including control plane transactions that update Status of resources into longevity test

Metadata

Metadata

Assignees

No one assigned

    Labels

    backlogCurrently unprioritized work. May change with user feedback or as the product progresses.testsPull requests that update tests

    Type

    No type

    Projects

    Status

    🆕 New

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions