Overview:

We have a somewhat unclear situation regarding whether ACS can officially be installed in namespaces other than "stackrox" or not.

This ticket was triggered by https://issues.redhat.com/browse/ROX-10921, which is about removing "this is unsupported" warnings from the ACS docs.

Technically we support this already (for example in ACS CS), but there are some caveats:

• Some default policies have the stackrox namespace hardcoded (see [slack thread|https://redhat-internal.slack.com/archives/C01DQH7UP8C/p1741692228647109).]
• We don't have proper e2e testing in-place for this (the scanner-v4-install tests actually deploy central and sensor to non-standard namespaces for some tests, but the coverage of these tests is very limited, they essentially just check if certain workloads come up healthy). The idea here is to change, e.g. the QA tests, to use non-standard namespaces.
• Central and Secured Cluster Services should be looked at separately as they might have different expectations in this regard.

If all looks good and proper testing is in place, all the warnings about non-standard namespaces should be removed from the documentation.