Implement the newly designed eventing-backend CRD

[nachtmaar]

In the proposal Add the Eventing backend CRD design proposal #671 a newly designed EventingBackend CRD is proposed. This ticket is about reflecting the changes in the EventingBackend Reconciler.

This ticket follows the following assumption: We only support one EventingBackend CR for now (the name and namespace of the eventing-backend are defined in the backend reconciler with default values). As soon as we support multiple active backends, this will change of course.

Tasks:

• [ ] Implement the newly designed eventing-backend CRD.
  • [ ] Add the Eventing Backend Ready condition type to the controller
  • [ ] Add spec.config support to the controller
• [ ] Switch to beb if spec.type=beb and spec.config.secretRef is valid
  • [ ] Implement eventing-backend reconciler to react on changes on new backend CR.
    • [ ] e.g. changing maxInflight is reflected on underlying eventing infrastructure

[github-actions[bot]]

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.

[k15r]

The eventing backend cr will be replaced by the eventing cr that comes with modular kyma