Skip to content

Crossplane is fighting with other XR condition owners when composition fails #6285

@sttts

Description

@sttts

What happened?

Compare https://github.com/crossplane/crossplane/pull/5450/files#r1951097798:

There might be other parties in the system that own conditions. This loop here will make Crossplane fight with them. Crossplane sets them to Unknown, the other controller update them to whatever they think is right.

How can we reproduce it?

Run a controller with a condition added to an XR. Then make the compose function fail, e.g. by having a pipeline step with an unknown function.

Then the controller and Crossplane fight over that 3rdparty condition.

What environment did it happen in?

Crossplane version: 1.18.2

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions