-
Bug
-
Resolution: Not a Bug
-
Normal
-
None
-
ACM 2.7.0
-
False
-
None
-
False
-
-
-
No
Description of problem:
ACM 2.7 / Submariner 0.14.1
When we are uninstalling the submariner components from the UI, we need to go to the "clusterset", switch to "Submariner Addon" tab, select the clusters and select Uninstall option.
This will remove the submariner components from the managed clusters.
But it leaves the broker information that tied with the clusterset, like global CIDR (in case of globalnet) and clusters id.
That information stored within the configmap.
From the UI, the only way to remove that information is to delete the clusterset.
But what should we do, if deletion of the clusterset is not possible.
For example, it could be used by other cluster which did not get submariner deployment.
In that case, the broker info is not deleted and if I'm redeploying the submariner, it could mismatch the deployment.
Of course, from the cli the configmap could be deleted explicitly.
The submariner-addon should be in charge of deleting the broker info once submariner got uninstalled from all the clusters within the clusterset.