Introduce ClusterCloudEventSource

[SpiritZhou]

Introduce ClusterCloudEventSource

Checklist

• When introducing a new scaler, I agree with the scaling governance policy
• I have verified that my change is according to the deprecations & breaking changes policy
• Tests have been added
• Changelog has been updated and is aligned with our changelog requirements
• A PR is opened to update our Helm chart (repo) (if applicable, ie. when deployment manifests are modified)
• A PR is opened to update the documentation on (repo) (if applicable)
• Commits are signed with Developer Certificate of Origin (DCO - learn more)

Relates to #3533

[tomkerkhove]

Did a quick skim and think it looks OK but not a go expert. @JorTurFer Can you share your wisdom?

[tomkerkhove]

Did a quick skim and think it looks OK but not a go expert. @JorTurFer Can you share your wisdom?

[wozniakjan]

I think this is on the right track, but I would like us to try to reduce the code duplication a bit ideally.

I created a sample PR to communicate my ideas better in #5924, most importantly I think we should explore some options to not copy-paste the reconciler. #5924 discusses one potential way how this might be achievable, ptal

[SpiritZhou]

I think this is on the right track, but I would like us to try to reduce the code duplication a bit ideally.

I created a sample PR to communicate my ideas better in #5924, most importantly I think we should explore some options to not copy-paste the reconciler. #5924 discusses one potential way how this might be achievable, ptal

Thanks @wozniakjan, I think triggerauthentication & clustertriggerauthentication can be refactor as well.

[wozniakjan]

Thanks @wozniakjan, I think triggerauthentication & clustertriggerauthentication can be refactor as well.

That is a good point, I will try to find some time later this month to check for any code duplication candidates for TA and CTA

[tomkerkhove]

/run-e2e cloud*
Update: You can check the progress here