Namespace scope support

[draveness]

Are we going to add a scope to change the namespace of a kubernetes object?

oam-kubernetes-runtime/pkg/workload/containerized/containerized.go

Lines 62 to 65 in 6b9e040

	// NOTE(hasheddan): we always create the Deployment in the default
	// namespace because there is not currently a namespace scheduling
	// mechanism in the Crossplane OAM implementation. It is likely that
	// this will be addressed in the future by adding a Scope.

[wonderflow]

What @hasheddan means is not changing the namespace of an existing kubernetes object. I think he means before a k8s object being create, the controller could use namespace scope to know which namespace the k8s object will go.

[draveness]

What @hasheddan means is not changing the namespace of an existing kubernetes object. I think he means before a k8s object being create, the controller could use namespace scope to know which namespace the k8s object will go.

Does it mean that the controller doesn't know the namespace of an kubernetes object, why not read the metadata field of an object?

[wonderflow]

This issue occurs in multi-cluster cases, one Application deployed in a master cluster will need some child parts which need to be deployed in remote clusters. The object in remote cluster need to know their namespace.

[draveness]

This issue occurs in multi-cluster cases, one Application deployed in a master cluster will need some child parts which need to be deployed in remote clusters. The object in remote cluster need to know their namespace.

SGTM, thanks for the clarification.