Goal Summary

This feature will change the default installation namespace for ACS (Stackrox) components from stackrox-* to openshift-acs-*. This change ensures consistency with other Red Hat OpenShift products, improves integration, and enhances the product's official branding and maturity.

Goals and Expected User Outcomes

The primary user, a Cluster Administrator or DevOps Engineer, will experience a more cohesive and integrated deployment of ACS within their OpenShift environment. The new namespace schema will align with Red Hat's product standards and may provide tighter integration with platform features like metric collection and more restrictive RBAC.

• Namespace Consistency: ACS components will now reside in namespaces (openshift-acs-*) that are consistent with other OpenShift-native products.
• Improved Integration: The new namespace will grant ACS workloads additional platform privileges, potentially improving functionality with the Observe tab and other OpenShift features without relying on brittle workarounds.

Acceptance Criteria

• The default installation namespaces for ACS must be changed from stackrox-central-services, stackrox-secured-cluster-services, and stackrox-operator to openshift-acs-central-services, openshift-acs-secured-cluster-services, and openshift-acs-operator respectively.
• The installation process must successfully deploy all ACS components into the new openshift-acs-* namespaces.
• The migration path for existing installations must be clearly defined and supported.
• The new namespace names must be reflected in all official documentation, installation guides, and manifest files.
• The change must not break any existing functionality or cause regressions in product behavior.
• The new namespaces must not cause any conflicts with other namespaces or products within an OpenShift cluster.
• All internal code references to the stackrox-* namespaces must be updated to openshift-acs-*.