manirajv06 commented on a change in pull request #277:
URL:
https://github.com/apache/incubator-yunikorn-k8shim/pull/277#discussion_r707424630
##########
File path: pkg/cache/application.go
##########
@@ -58,6 +58,7 @@ type Application struct {
placeholderAsk *si.Resource // total placeholder request
for the app (all task groups)
placeholderTimeoutInSec int64
schedulingStyle string
+ requestOriginatingPod *v1.Pod // Original Pod which creates the
requests
Review comment:
@wilfred-s @yangwwei Thanks for sharing your thoughts.
Given the current limitation in some cases and future plans, Can we do the
following?
1. Filing a separate JIRA for aggregation in general for all places (not
just only for this particular case). This JIRA can focus mainly on how to make
life easier on monitoring aspects by aggregating all such events. Also,
destination has to be fixed across different scenarios because expecting Admin
to go over 'n' number of different places to look for events is difficult for
them during troubleshooting.
2. Filing a separate JIRA to take care of these kind of events notifications
wherever we have operator integration as of now. If needed we can do this.
Otherwise, we can cover this in above JIRA itself.
3. Given the above plans, Can we push this PR as an interim solution?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
