Closed zhujian7 closed 2 years ago
// defaultSpokeComponentNamespace is the default namespace in which the spoke agent is deployed defaultSpokeComponentNamespace = "open-cluster-management"
I am not quite sure if https://github.com/open-cluster-management-io/registration/blob/main/pkg/spoke/spokeagent.go#L45 should be changed to "open-cluster-management-agent"
Is this defaultSpokeComponentNamespace
only useful for tests?
// defaultSpokeComponentNamespace is the default namespace in which the spoke agent is deployed defaultSpokeComponentNamespace = "open-cluster-management"
I am not quite sure if https://github.com/open-cluster-management-io/registration/blob/main/pkg/spoke/spokeagent.go#L45 should be changed to "open-cluster-management-agent" Is this
defaultSpokeComponentNamespace
only useful for tests?
We also use open-cluster-management-agent
as the default namespace in registration-operator, so I think we may change this to keep the consistent
/cc @qiujian16 what's your opinion?
yes, I think we should change it to open-cluster-management-agent
/approve /lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: qiujian16, zhujian7
The full list of commands accepted by this bot can be found here.
The pull request process is described here
This PR supports deploying registration control plane and agent in two separate clusters and in different namespaces. It is good for new guys to understand the registration.
Signed-off-by: zhujian jiazhu@redhat.com
cc @qiujian16 @skeeey