search

operator-framework / operator-controller

A new and improved management framework for extending Kubernetes with Operators
https://operator-framework.github.io/operator-controller/
Apache License 2.0
73 stars 54 forks source link

Consolidate the namespace creation manifest in to a single repository #1138

Open LalatenduMohanty opened 3 months ago

LalatenduMohanty commented 3 months ago

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 commented 3 months ago

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.