search

openshift / compliance-operator

Operator providing OpenShift cluster compliance checks
Apache License 2.0
110 stars 110 forks source link

Support deployments on all namespaces #748

Closed JAORMX closed 3 years ago

JAORMX commented 3 years ago

This ensures that we support that the operator listens on all namespaces. While this is not a big nor difficult change by itself, it does require us to make a decision on where to deploy the default profiles/profilebundles.

In the case where the operator is deployed on all namespaces, only the operator namespace (openshift-compliance if using the recommendation) will get our defaults.

Signed-off-by: Juan Antonio Osorio Robles jaosorior@redhat.com

mrogers950 commented 3 years ago

/test all

JAORMX commented 3 years ago

/test all

openshift-ci[bot] commented 3 years ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JAORMX, Vincent056

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files: - ~~[OWNERS](https://github.com/openshift/compliance-operator/blob/master/OWNERS)~~ [JAORMX,Vincent056] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment
Vincent056 commented 3 years ago

@JAORMX I have some questions, I am wondering if the operator gets deployed on all-namespace, it will only have one instance of CO?

And if the profiles get deployed on openshift-compliance, is it also accessible by the CO deployed on all-namespace?

openshift-bot commented 3 years ago

/retest-required

Please review the full test history for this PR and help us cut down flakes.