Yuan (Bob) Gong

ml-pipeline service is monitored here, it only expose metrics about the entire cluster for now. Welcome new requests to add metrics

I think that sounds like a fair argument, but regarding project status, we are transitioning to v2, so it's better reconsider this feature request after other critical features are ready.

@discordianfish @jonasdebeukelaer Instead of editing a Job directly, I'm thinking about an alternative: ``` 1. disable the job (existing runs won't be removed) 2. clone the job and change the...

@discordianfish I agree these are implementation details, it was more of a discussion in the context of where we want to go for #3788. You are welcome to stick to...

I synced with @jingzhang36 today, our conclusion for Job is: 1. We'll provide these features as is, if cloning a Job doesn't work for you, please use other alternatives like...

@discordianfish Thanks for explaining the confusions you are getting! I agree it would be a painful experiencing spending a lot of pain writing a PR, but not seeing it being...

> Fair enough. So you are okay with merging the PR if the ScheduledWorkflowController handles this as expected? If that's the case, I can spend time creating a cluster to...

Thanks for the suggestions for community support. I'll surface that for internal discussion. Yes, and `Eventually clean up the old job` is not a necessary requirement. If we want to...

also FYI, our documentation for generated client just got sooo much better than before: https://kubeflow-pipelines.readthedocs.io/en/latest/source/kfp.server_api.html#kfp_server_api.api.job_service_api.JobServiceApi.list_jobs

> @bobgy Okay my plan (essentially) is to redo our CI scripts: > > - upload new job and set version=git-sha in description > - deactivate all jobs with version!=git-sha...