Summary:

Customers would like to undstand how Red Hat Advanced Cluster Security (RHACS) provides continuous security posture and swift recovery from failures or disasters, by addressing critical data loss and operational continuity challenges during Central outages. This empowers customers, particularly those with stringent requirements like financial institutions, to deploy RHACS with confidence in critical production environments and recover swiftly from catastrophic events.

Expected end user outcomes :

Security and platform administrators will be able to deploy and configure RHACS for high availability, ensuring core security services (e.g., Central, Scanner, Collector communication) maintain operation even if individual components fail. They will also be able to implement effective disaster recovery strategies, including solutions for restoring RHACS instances and their data across clusters with differing names. This is critical for customers who require a robust DR plan to sign off on production deployments.  

GOALS FOR DISCOVERY FEATURE RELEASE:

• {}Document HA/DR best practices{}
• {}Identify gaps we have in our solution{}
• {}Create a clear plan to address gaps in future.{} 

Acceptance Criteria:

• Operational Documentation:
  • Clear guidance is provided for configuring and validating availability, DR, and failover behavior across supported platforms.

Success Criteria or KPIs measured:{}

Customers are able to use documented best practices to configure RHACS which would directly result in:

• Fewer issues from customers around Central outages
• Fewer issues from customers around downtimes and outages of other ACS components 

Out of Scope :

THIS RELEASE DOES NOT INTEND TO PROVIDE:

• Any actual implementation or usage changes
• Design to address all gaps - we will build on the list of gaps and try to come up with detailed design to address each in releases following this one.