Mark ProviderConfigs as Available when ready for use.

[djeremiah]

What problem are you facing?

Right now, it is possible to create ProviderConfigs as part of a Composition, but the composition never transitions to a Ready status. This appears to be because even though the provider is able to create the ProviderConfig, the reconciler does not mark it Available like is done with managed resources.

How could Crossplane help solve your problem?

The providerconfig.Reconcile function could mark ProviderConfigs as Available.

[bobh66]

I have several compositions that create ProviderConfigs and the composites get to the Ready state, so this may be a different issue with the composite/composition.

[haarchri]

https://github.com/upbound/platform-ref-aws/blob/main/package/cluster/eks/composition.yaml#L227 set readinessCheck to none

[negz]

What does "available" mean for a ProviderConfig? Just that it exists?

In the very early days of Crossplane we set an Available / Ready condition on a ProviderConfig based on some test - e.g. whether the ProviderConfig could be used to list buckets. This was fairly pointless though - being able to list buckets doesn't mean a ProviderConfig will work for what you really want to use it for.

[github-actions]

Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as stale because it has had no activity in the last 90 days. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.