Bug 1867607

Summary: namespace of cluster should not need to be the same as the cluster name
Product: Red Hat Advanced Cluster Management for Kubernetes Reporter: raffaele spazzoli <rspazzol>
Component: Cluster LifecycleAssignee: Hao Liu <haoli>
Status: CLOSED WONTFIX QA Contact: magchen@redthat.com <magchen>
Severity: unspecified Docs Contact: Christopher Dawson <cdawson>
Priority: unspecified    
Version: rhacm-2.0.zCC: ckavili, gghezzo
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-09-22 02:39:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description raffaele spazzoli 2020-08-10 13:13:28 UTC 
Description of problem:
When a cluster is created via the webui all the resources relative to it are put in a namespace that is named as the cluster. This seems a nice default.
When creating a cluster from the CLI, there should be no constraint on the namespace in which all of the hive and RHACM resources are created.
Today of the name of the namespace is not the same as the cluster name, the cluster is created, but it is not linked to the web ui console.
The cluster remains in "pending" state for ever because the klusterlet resources are not correctly created in the managed cluster. These resources are not created because the syncset is never created. The sycnset is never created because the ACM operator expects the cluster name and namespace name to be the same.


Version-Release number of selected component (if applicable): 2.x


How reproducible: 100%


Steps to Reproduce:
create the needed ACM resources as per yaml panel in the webui, but in a namespace that is not the same as the cluster name.

Actual results:
cluster is created, but never linked to ACM. Pending state for ever.


Expected results:
cluster is created and linked.
Comment 1 Ginny Ghezzo 2020-09-22 02:39:31 UTC 
Raffaele, 
Thank you for the recommendation and feedback. After review we have made a decision to map the namespace and names and for now will not be revisiting.

Thank you, 
Ginny