-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
1.16.1
-
5
-
False
-
-
False
-
-
-
GitOps Tangerine Sprint 22
Description of Problem:
The customer reported issues with the GitOps operator sharding after its implementation. Specifically, clusters occasionally entered an unknown state,
requiring manual restarts of the controllers to restore functionality.
The distribution of clusters among the controllers is uneven, with some controllers managing no clusters and others handling more than one.
Additional Info:
Client have been reporting an issue where they have observed few of the clusters which are been managed by Gitops are getting disconnected.
The customer configured sharding with 5 replicas and the legacy sharding algorithm. The customer further updated the configuration to use 8 shards with the legacy algorithm, but the problem remained unresolved.
Problem Reproduction:NA
Reproducibility: Intermittent
Prerequisites/Environment:
openshift-gitops-operator.v1.16.1
ACM
Expected Results:
Clusters should remain in connecting state.
Actual Results:
The clusters are getting disconnected sometimes as reported by the client.