Anton Gilgur

> This PR brings in the "once a day" documentation from #13365 As requested in https://github.com/argoproj/argo-workflows/pull/13474#pullrequestreview-2242246764

> @agilgur5 Sir, seems like contributors involved in #3719 didn't submit commit lately, can you take a look at this issue and give some suggestions? I'm not sure what you...

I would continue discussing with @Joibel and wait for a response from him if you don't believe the previous proposal is sufficient. Waiting a few days or even a week+...

> 651e199a20c96319c4bd9d24c084a1de9f2e62725749a9f239adfb785147299b That commit SHA 404s for this repo: https://github.com/argoproj/argo-workflows/commit/651e199a20c96319c4bd9d24c084a1de9f2e62725749a9f239adfb785147299b

Oh, this is an image digest: https://hub.docker.com/layers/argoproj/workflow-controller/latest/images/sha256-651e199a20c96319c4bd9d24c084a1de9f2e62725749a9f239adfb785147299b

I believe this requires `?logOptions.container=main` or another `container` selection

> According to https://cloud.google.com/kubernetes-engine/docs/concepts/cluster-upgrades, > `UPDATE_CLUSTER means an update not changing the Kubernetes control plane version` and `google.container.v1.ClusterManager.PatchCluster` means `a cluster configuration change`. Or, in standard k8s terms, this seems...

> It seems that the problem is with the `Patch` k8s API request, it is not updating the cron status, so whenever it syncs again it retriggers the workflow. >...