Enhancement: discrete CRD / CR creation install phases

[grokspawn]

operator-sdk/internal/olm/installer/client.go

Lines 88 to 91 in 861f524

	log.Print("Creating CRDs and resources")
	if err := c.DoCreate(ctx, objs...); err != nil {
	return nil, fmt.Errorf("failed to create CRDs and resources: %v", err)
	}

Enhance to have separate CRD installation phase and CR creation phase. As currently sorted, the order of the objects created will already respect this sequence, but it would be nice to separate them out for auditing, error handling, etc.

Referred to in #6490 (review)

[acornett21]

@grokspawn @everettraven DoCreate already has audit logging on which resource is being created, and which one fails, if any. Is this logic not enough? Please see here:

https://github.com/operator-framework/operator-sdk/blob/master/internal/olm/client/client.go#L116-L121

[everettraven]

@acornett21 That safeCreateOneResource function was added recently to retry resource creation due to CRDs not yet being "ready" on the cluster blocking the creation of the custom resource. IIRC the creation logic currently issues creation requests for the CRDs and then immediately starts to try creating the custom resources. The inspiration behind this issue is that it would be nice if we could ensure that the cluster has processed the CRDs and is ready to accept requests for these custom resource before attempting to create the custom resources.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale