search

IBM / cloudpak-gitops

Deployment of IBM Cloud Paks using ArgoCD / Red Hat GitOps operator.
Apache License 2.0
22 stars 23 forks source link

Custom namespaces cause conflict between Argo and RHACM configuration #66

Closed nastacio closed 2 years ago

nastacio commented 2 years ago

Describe the bug Labeling an OCP cluster with the label cp4i:mycloudpak makes Argo CD and RHACM "fight" with one another over the desired state of the target cluster. For whatever it is worth, this problem was observed in an OCP cluster version 4.6.

When accessing the Argo CD console, the cp4i-app tile keeps alternating between an out-of-sync and in-sync state. I've included pictures below. They alternate between the mycloudpak namespace and the ibm-cloudpaks namespace (the default for installation of all Cloud Paks.)

To Reproduce Steps to reproduce the behavior:

  1. Create an OCP cluster 4.6 cluster, with sufficient capacity to deploy the Cloud Pak for Integration.
  2. Register the cluster on a RHACM server
  3. Label the cluster with cp4i:mycloudpak
  4. Observe the error

Expected behavior After RHACM pushes the Argo Application resources for the Cloud Pak for Integration, it should be deployed to the mycloudpak namespace, then Argo should report the applications as synchronized and healthy, while RHACM should report the governance policy as being met.

Screenshots image image

Additional context Add any other context about the problem here.