Why reconcile run Twice and How can i run it Once ?

[ppsite]

let client = Client::try_default().await?;
let deployments: Api<Deployment> = Api::all(client);

Controller::new(deployments, Default::default())
    .run(reconcile, error_policy, Arc::new(()))
    .for_each(|_| futures::future::ready(()))
    .await;

Ok(())

As code above, when i Change a Deployment Annotation, reconcile run Twice, Considering performance issues, I look forward to executing it only once;

apiVersion: apps/v1
kind: Deployment
metadata:
  annotations:
    xxx/deploy: "2"   # value chanaged: 1 -> 2

Is there someone who can explain and guide me forward ?

[SOF3]

Maybe another controller (e.g. deployment controller) also updated the deployment in response to your change and triggered another reconcile? You can try dumping the whole deployment object to see if anything changed.

[ppsite]

I guess so: deployment controller triggered another reconcile;

apiVersion: apps/v1
kind: Deployment
metadata:
  annotations:
    xxx/deploy: "2"   # value chanaged: 1 -> 2

Is there anyway to find out, what changed in the CR to trigger the reconcile ?

One Annotation changed, BUT got the Hole CRD, i wanna do something according to CHANGES;

[SOF3]

The idea of "reconcile" is eventual consistency, where the controller recompute all states it is in charge of whenever something changes. Otherwise you will miss the changes that you did not observe when the controller is down and restarted.

[ppsite]

Thank U very much !!! 👍🏻

[clux]

it's also possible to filter out changes to a controller that did not affect the spec using something like WatchStream::predicate_filter on appropriate predicate. This does require the more advanced streams interface however.