Loading...

XML

Word

Printable

Type: Feature Request
Resolution: Unresolved
Priority: Normal
Fix Version/s: None
Affects Version/s: None
Component/s: GitOps
Labels:
None

Target Version:
None
Activity Type:
Product / Portfolio Work
Status Summary:
None
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Products:
None
Hierarchy Progress Bar:
None

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

PX Review Complete:
None
PX Impact Score:
PX Impact Range:
None
PX Priority Data:
None
PX Technical Impact:
None
PX Technical Impact Notes:
None
PX Scheduling Request:
None

1. Proposed title of this feature request

Make antiAffinity and affinity rules configurable in the argocd operator (OpenShift GitOps Operator)

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

We are missing a way to configure the Affinity AntiAffinity for the ArgoCD ApplicationController itself. We have seen that AntyAffitnity rules are set by default. However, these only prevent multiple replicas of the Application Controller from running on the same host. However, we want to distribute the application controllers to several data centers/zones of our cluster. In our opinion, separate affinity and antiAffnity rules would be the correct way to achieve this.

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

We want to distribute the ArgoCD pods across multiple datacenters/zones to improve availability in case of a datacenter outage

4. List any affected packages or components.

OpenShift GitOps Operator (ArgoCD)

Assignee:: Harriet Lawrence

Reporter:: Satyam Burhade

Need Info From:: None

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Created:: 2025/02/12 7:08 AM

Updated:: 2025/07/03 1:23 PM

Target start:: None

Target end:: None

Details

Description

Attachments

Easy Agile Planning Poker

Activity

People

Dates