Skip to content

feat: As a user, I want to reduce the risk of full configuration delivery failure caused by APISIX Ingress Controller, so that the impact is limited to the block level where the affected Ingress resides #2765

Description

@Goend

Description

As a user, I want APISIX Ingress Controller to isolate invalid or failed configuration changes to the smallest possible block scope, rather than causing the full gateway configuration delivery to fail, so that during
cold start or full synchronization, a single bad Ingress-related configuration does not block all other valid configurations from being delivered successfully.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions