Consolidate the namespace creation manifest in to a single repository

[LalatenduMohanty]

We have the namespace manifest in both operator-controller [2] and catalogd [1]. However install script [3] applies both one after another. Ideally the namespace should be in just catalogd. Also the pod-security.kubernetes.io/enforce is different in both the repos which needs to be fixed as well i.e. pod-security.kubernetes.io/enforce: baseline vs pod-security.kubernetes.io/enforce: restricted [1] [2]

[1] https://github.com/operator-framework/catalogd/blob/main/config/base/manager/manager.yaml [2] https://github.com/operator-framework/operator-controller/blob/main/config/base/manager/manager.yaml [3] https://github.com/operator-framework/operator-controller/blob/main/scripts/install.tpl.sh

[bentito]

Couldn't someone, for dev testing, etc, still want to run just operator-controller? If the deploy/run targets lack the NS deploy they will fail since catalogd hasn't been installed. Is there a drawback to just keeping and let it do nothing when catalogd has been installed already? Seems like it keeps the two components better decoupled to keep them both installing the NS.

[github-actions[bot]]

Issues go stale after 90 days of inactivity. If there is no further activity, the issue will be closed in another 30 days.

[github-actions[bot]]

This issue has been closed due to inactivity.