Watcher-Listener delivery

[tobiscr]

Description

The Change Detection mechanism is is an essential component in the new reconciler architecture. It is responsible to detect configurations provided by the customer and make them available on the management plane.

This mechanism consists of a two elements:

• a watcher component running inside of a customer cluster and detecting changees
• listener component running on the management plane side.

The watcher component It is following the K8s operator pattern identifying configuration changes applied by the customer (via ConfigMaps). It propagates such changes to the listener component. The listener persists the change in the management plane. It will be picked up by the Kyma Operator who injects the customer configuration values into the related component CRs.

Acceptance criteria

• runtime-watcher(MVP): Implement OCI bundle which enables the Module-Manager to install the Watcher component #3
• runtime-watcher(MVP): Implement Watcher component for SKR #5
• runtime-watcher(MVP): Implement Listener endpoint API #6
• runtime-listener: Re-implement watcher event type #62
• Runtime-watcher: Enhance KCP watcher reconcile loop implementation #67
• CI/CD pipelines are created and executed for code changes
• Threat modelling findings implemented (see Security for new reconciler architecture lifecycle-manager#144)
  • Security: Identification / authentication for watcher requests lifecycle-manager#147
  • Security: Payload validation for watcher requests lifecycle-manager#148
  • Security: Match Kyma-CR-Domain with SAN from Watcher request lifecycle-manager#149
• Operational requirements are covered
  • Exposing analysis and statistic relevant data via Prometheus endpoint
  • Logging of critical events
  • Auditlog is integrated (only required for sensitive actions or data changes)
  • Operational test was executed and trouble-shooting guides were created
    • What would happen if the watchable resources increase with time. Rate limiting or comparison based on filtered set timestamps?
• Documentation of the architectural design
• Microdelivery process established

Issues
kyma-project/kyma#13759

Appendix

• CRD = Customt Resource Definition
• CR = Custom Resource
• BYOC = Bring your own cluster
• SKR = SAP Kyma Runtime

[kyma-bot]

This issue or PR has been automatically marked as stale due to the lack of recent activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

• After 60d of inactivity, lifecycle/stale is applied
• After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Close this issue or PR with /close

If you think that I work incorrectly, kindly raise an issue with the problem.

/lifecycle stale

[kyma-bot]

This issue or PR has been automatically marked as stale due to the lack of recent activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

• After 60d of inactivity, lifecycle/stale is applied
• After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Close this issue or PR with /close

If you think that I work incorrectly, kindly raise an issue with the problem.

/lifecycle stale