1. Proposed title of this feature request

Enable Editing Compliance Operator ScanSetting and ScanSettingBinding Parameters from RHACS Console

2. What is the nature and description of the request?

Currently, Red Hat Advanced Cluster Security for Kubernetes (RHACS) can trigger and schedule compliance scans, but it does not allow users to modify the underlying Compliance Operator ScanSetting or ScanSettingBinding parameters (e.g., scanTolerations, nodeSelectors, or other scan execution settings) directly from the console.

The request is to enhance RHACS so that users can edit relevant ScanSetting and ScanSettingBinding parameters directly when creating or scheduling compliance scans. This would reduce the need for manual CR edits, streamline scan configuration, and improve operational efficiency.

3. Why does the customer need this? (List the business requirements here)

• Centralized Management: Configure and manage all scan settings from the RHACS console without accessing the cluster directly.

• Operational Efficiency: Eliminates manual edits to ScanSetting or ScanSettingBinding CRs.

• Consistency Across Clusters: Ensures uniform scan configuration in multi-cluster environments.

• Supports Automation and GitOps: Enables programmatic or UI-driven configuration while maintaining alignment with automated compliance workflows.

• Error Reduction: Reduces risk of misconfiguration from manual edits.

• Future Flexibility: Supports enhancements like tolerations, node selectors, or other scan-specific parameters without additional CR edits.

4. List any affected packages or components.

• RHACS Console – UI/UX for scan creation, scheduling, and configuration.

• RHACS Backend/Controller – handles interactions with Compliance Operator CRs (ScanSetting and ScanSettingBinding).

• OpenShift Compliance Operator – ScanSetting and ScanSettingBinding custom resources responsible for scan execution.