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

feat: Make Cert Manager OperatorGroup configurable #313

Closed nastacio closed 9 months ago

nastacio commented 9 months ago

Is your feature request related to a problem? Please describe. CP4I 2023.4 installation now requires the pre-deployment of a cert manager.

Other Paks also need to deploy a cert manager, so it is important that we make the "OperatorGroup" name configurable, aligning it with the names used by other Cloud Paks that may be later installed to the cluster.

Describe the solution you'd like

  1. Add a new configuration parameter for the Job in config/cloudpaks/cp-shared/operators/templates/0050-sync-cluster-scoped-operators.yaml, indicating the name for the OperatorGroup to be created.
  2. The repo should also be smart to recognize whether the target namespace for the cert manager operator already has an OperatorGroup and not create a new one.

Describe alternatives you've considered None.

Additional context Found this problem while trying to install CP4BA manually to a cluster where CP4I had already been installed.

nastacio commented 9 months ago

:tada: This issue has been resolved in version 0.36.1 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket: