-
Notifications
You must be signed in to change notification settings - Fork 225
Conversation
cd179ba
to
ebf16a7
Compare
/ok-to-test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, just one last sticking point 😛
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just curious why not utilize this so we don't need to have something running continuously.
https://kubernetes.io/docs/tasks/job/automated-tasks-with-cron-jobs/
@vaikas-google, The reason I didn't use k8s CronJob was put in the commit message, there's an issue with batched job if it has a sidecar, it can not run to completed status, see the issue below. And we can not disable istio-proxy sidecar otherwise it can not talk to the sink. |
/lgtm |
@whynowy /lgtm |
:) It looks like I need to rebase... doing it. |
Used Deployment as receive adapter instead of CronJob because of the batched job side car issue. kubernetes/kubernetes#25908 If this issue is resolved in the future, we can switch to use CronJob.
210ebca
to
4eed8cd
Compare
@Harwayne @vaikas-google - rebased and updated the code to use unstructured client for dynamic objects |
The following is the coverage report on pkg/.
|
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vaikas-google, whynowy The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Used Deployment as receive adapter instead of CronJob because of
the batched job side car issue.
kubernetes/kubernetes#25908
If this issue is resolved in the future, we can switch to use CronJob.
Proposed Changes