Usages between ClusterScope Compositions and Namespaces resources

[jkroepke]

What happened?

If a Composition is closter scoped and created a namespaces scoped resource, a ClusterUsage will be created (thats correct), but the spec.by resources is missing a namespace. This results into unready usages, because of the missing namespace field for namespace scoped resources.

Ref: Missing check, if resource is namespaced:

function-sequencer/fn.go

Lines 233 to 255 in 7759428

	usage := map[string]any{
	"apiVersion": ProtectionGroupVersion,
	"kind": usageType,
	"metadata": usageMeta,
	"spec": map[string]any{
	"by": map[string]any{
	"apiVersion": by.GetAPIVersion(),
	"kind": by.GetKind(),
	"resourceRef": map[string]any{
	"name": by.GetName(),
	},
	},
	"of": map[string]any{
	"apiVersion": of.GetAPIVersion(),
	"kind": of.GetKind(),
	"resourceRef": map[string]any{
	"name": of.GetName(),
	},
	},
	"reason": DependencyReason,
	"replayDeletion": rd,
	},
	}

How can we reproduce it?

Create a composition (cluster-scoped) which created namespace scoped resource and configure a sequence between it. (create cluster scoped namespace first, than a namesapce scoped configmap)

What environment did it happen in?

Function version: 0.5.0

[bobh66]

@jkroepke if I understand this correctly, the namespace of the configmap should be included here?

[jkroepke]

Currently, I got this error:

cannot get using: an empty namespace may not be set when a resource name is provided

and the ClusterUsage will unready for ever. However, the ClusterUsage does not have an field like spec.by.namespace. It's seems like ClusterUsage does not support the usecase that a namespaced Object has an usage of an cluster scoped object.

In that case, it may makes more sense to NOT create a ClusterUsage until it solved in core.

[jkroepke]

See crossplane/crossplane#7123