IHAC who is experiencing the "KubeDeploymentGenerationMismatch" alert for the gitops-plugin in multiple clusters within the openshift-gitops project.
We attempted to resolve the issue by updating the replica count in the deployment, which caused the alert to disappear temporarily, but it was triggered again shortly after. Are there any other reasons that I should investigate to address this issue permanently?
We tried below :
~~~
1. increase the replica set :  oc scale --replicas 3 deployment.apps/<deployment-name>
2. deployment rollout restart: oc rollout restart deployment/gitops-plugin
3. Delete the deployment:
~~~
$ oc scale deployment gitops-plugin --replicas=0 -n openshift-gitops
deployment.apps/gitops-plugin scaled

$ oc delete deployment gitops-plugin -n openshift-gitops
deployment.apps "gitops-plugin" deleted
~~~


Extra details : 
## Alert: 
~~~
alertname = KubeDeploymentGenerationMismatch
container = kube-rbac-proxy-main
deployment = gitops-plugin
endpoint = https-main
job = kube-state-metrics
namespace = openshift-gitops
openshift_io_alert_source = platform
prometheus = openshift-monitoring/k8s
service = kube-state-metrics
severity = warning
Annotations
description = Deployment generation for openshift-gitops/gitops-plugin does not match, this indicates that the Deployment has failed but has not been rolled back.
summary = Deployment generation mismatch due to possible roll-back
~~~

    - Not reproducible

    1.
    2.
    3.
    

    ## Case ID: 03840705 (Inspect report is present in the case)