Exploring the Feasibility and Implications of Multiple Non-Admin Controllers in a Cluster

[mpryc]

Currently it is possible to create multiple separate OADP instances in one cluster.

Allow to have multiple Non Admin Controllers within one cluster is a decision to be made with pros/cons to consider.

Allowing multiple Non Admin Controllers needs to answer questions:

• Should there be a restriction on having only one controller per OADP instance deployed by the OADP deployment?
• How can we ensure that multiple controllers do not concurrently react to the same Non-Admin Backup objects?
  • Implement namespace filtering for each Non-Admin Controller to limit the namespaces they monitor.
  • Utilize label-based filtering for each Non-Admin Controller to restrict the namespaces they observe.
  • Combine both namespace and label filters for enhanced control.
• Is it advisable to generate an error for a new Non-Admin Controller if the namespace it aims to operate within is already managed by another Non-Admin Controller within the same cluster?