Skip to content

[epic] Ensure no two ClusterExtensions manage the same underlying object when concurrent reconciles > 1 #1101

Open
@everettraven

Description

@everettraven

As mentioned in #736 , Helm has support for ensuring the same resources are not managed by multiple Helm Releases. This is sufficient when there is no concurrent reconciliation possible, but we will need to come up with an alternative solution that prevents race conditions when concurrent reconciliation is allowed.

Metadata

Metadata

Assignees

Labels

epicv1.xIssues related to OLMv1 features that come after 1.0

Type

No type

Projects

Status

No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions