With the move of CronJob sources to the main eventing controller, folks need to delete the knative-sources namespaces when then upgrade from 0.5.x to 0.6.0.
Otherwise we experience creation of multiple CronJob pods.
Deleting the namespace knative-sources got us back to a good working state with regards to cronjob sources.
So hold on this.
Looks like the error we saw was caused because eventing-sources was on a released version and we upgraded eventing to HEAD.
Yeah, no need to do this if you upgrade both components to 0.6.0
/close
@n3wscott: Closing this issue.
In response to this:
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
sorry for the noise, but I can confirm if you keep eventing and eventing-sources in sync cronjob and the other sources work well.