Simon_CQK
Simon_CQK
@llinvokerl hi llinvokerl, would you contribute the proposed feature to the community? If so, I will assign it to you :)
> @SimonCqk please review. nice work!
@sbdtu5498 LGTM in my view, anyway, can you add some unit tests for this feature?
> Sure thing! Also, do you think it would be a good idea to have two different historyLimit e.g. successfulHistoryLimit and failedHistoryLimit, to give more freedom to users over which...
@sbdtu5498 hi, it seems that UT/e2e checks failed, would you rebase upstream master branch and add more tests, then the PR can move on!!
@13241308289 Hi, thanks for the feedback! The reason we didn't initially include this label was due to the limited capacity of Prometheus's data backend, which doesn't actively purge data that's...
> I took another look at the code, and it turns out that this metric is initialized at the controller layer, which is why it's not possible to expose the...
I'll review ASAP
btw, PR conflicts with master branch