Description of problem:
Should forbid the creation of a subscription under a namespace without an operatorgroup object
Version-Release number of selected component (if applicable):
$ oc exec olm-operator-5f7dcdcd8f-ttn7t -- olm -version
OLM version: 0.8.0
git commit: 75e95a0
Steps to Reproduce:
1. Create a new ns
$ oc create ns federation-system
2. Create subscription.
$ cat subscription.yaml
$ oc create -f subscription.yaml
Subscription is created successfully, but no workload Pod is created.
Subscription can not be created.
Because OLM is not an apiserver (it uses CRDs), we can't actually prevent the creation of the object itself. The important part is that the Subscription is not noticed and no operators are installed.
We could fix this through an additional component (validating admission webhook) - but that would be a large thing to add at this point. Could we track this as a feature request for a future version?
Will we make the Subscription is noticed in openshift 4.0?
> We could fix this through an additional component (validating admission webhook) - but that would be a large thing to add at this point.
We should address this issue. So could you help transfer it to the appropriate component?
> Could we track this as a feature request for a future version?
Sure, we can change this bug as a feature request, and we should highlight this issue in our release document.
@Qin What do you suggest?
This has been sitting here for a while. It's not a bug, it's intended behavior. We can add Subscription ignoring logic, but as Evan stated, this would be a new feature. Can we get this report removed?
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.