### Environment * How did you deploy Kubeflow Pipelines (KFP)? <!-- For more information, see an overview of KFP installation options: https://www.kubeflow.org/docs/pipelines/installation/overview/. --> * KFP version: <!-- 2.0.3 To find the version number, See version number shows on bottom of KFP UI left sidenav. --> * KFP SDK version: <!-- 2.4.0--> ### Steps to reproduce <!-- Throttle disk I/O on the storage backing kfp-db to approximately 5 IOPS. Either programmatically or via misconfiguration, whoops. Submit one or more pipeline runs via the KFP UI or SDK while the database is under this degraded I/O constraint. Observe the Kubernetes resources, created to back the run, namely Argo Workflows.. --> ### Expected result <!-- The pipeline run should start and complete successfully. The garbage collector in resource_manager.go should not treat a workflow as orphaned unless it has confirmed that no corresponding database entry exists, accounting for in-progress writes. --> Impacted by this bug? Give it a 👍.
Environment
Steps to reproduce
Expected result
Impacted by this bug? Give it a 👍.