Pasha Kostohrys

@CodiumAI-Agent /review

I think it is good idea, dont see any reason why we need always. But we need resolve issue with latest tag first, which we use in master branch. This...

@daengdaengLee See https://stackoverflow.com/questions/74006353/difference-between-always-and-ifnotpresent-imagepullpolicy If you use IfNotPresent and the image with the specified tag is already present on the worker node, Kubernetes will use that image to start the container,...

Yes, it can be an option. But maybe if you need such scenario, it will be easier if you modify manifests with kustomize by your own ?

Will review. Sorry for delay

@ragnarpa Taking a look

Hey @patrick-tang , thank you for your contribution. Your change also covered in this PR https://github.com/argoproj/notifications-engine/pull/339/files . I think it will be better just merge last one because it covers...

Closing it, but again, thank you for your contribution @patrick-tang . Next time just assign review to me, so i can see it in notifications

@CodiumAI-Agent /review

@reggie-k i think as follow up PR it would be nice to provide dashboard that will show usage of these metrics