Skip to content
This repository has been archived by the owner on Jun 8, 2022. It is now read-only.

Namespace scope support #18

Closed
draveness opened this issue May 8, 2020 · 4 comments
Closed

Namespace scope support #18

draveness opened this issue May 8, 2020 · 4 comments

Comments

@draveness
Copy link

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

// 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
Copy link
Member

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
Copy link
Author

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
Copy link
Member

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
Copy link
Author

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants