have an issue with ObservedObjectCollection in provider-kubernetes - When I start using them, all other objects with spec.readiness.policy set to DeriveFromObject become extremely slow.
It takes up to 15 minutes to get the status updated, whereas without ObservedObjectCollection, it takes around 5 minutes. The ObservedObjectCollection is not used in combination with these other objects - they are independent of each other
Also, the observed objects are not created - it takes around 15-25 minutes.
Interestingly, when I switch spec.readiness.policy to default, all resources are created immediately.
So, something is blocking when using ObservedObjectCollection in combination with objects that have DeriveFromObject set for spec.readiness.policy
What happened?
have an issue with ObservedObjectCollection in provider-kubernetes - When I start using them, all other objects with
spec.readiness.policy
set toDeriveFromObject
become extremely slow. It takes up to 15 minutes to get the status updated, whereas withoutObservedObjectCollection
, it takes around 5 minutes. The ObservedObjectCollection is not used in combination with these other objects - they are independent of each otherAlso, the observed objects are not created - it takes around 15-25 minutes. Interestingly, when I switch
spec.readiness.policy
to default, all resources are created immediately. So, something is blocking when using ObservedObjectCollection in combination with objects that have DeriveFromObject set forspec.readiness.policy
How can we reproduce it?
What environment did it happen in?
Crossplane version: