Lifecycle Manager delivery

[tobiscr]

Description The Lifecycle Manager is an essential component in the new reconciler architecture. It is following the K8s operator pattern reacting on data changes (defined in CRs).

The Lifecycle manager is responsible for the lifecycle management of Kyma installations (respectively the components configured for a Kyma cluster) and determining the Kyma installation status (aka. cluster status).

Acceptance criteria

• [x] #77
• [x] #78
• [x] #49
• [x] Documentation of the architectural design
• [ ] Operational requirements are covered
  • [x] #79
  • [x] Exposing analysis and statistic relevant data via Prometheus endpoint
  • [x] Logging of critical events
  • [x] Auditlog is integrated
  • [ ] Operational test was executed and trouble-shooting guides were created
• [ ] Threat modelling findings implemented (see https://github.com/kyma-project/lifecycle-manager/issues/144)
  • [ ] https://github.com/kyma-project/lifecycle-manager/issues/13
  • [x] https://github.com/kyma-project/lifecycle-manager/issues/146
• [ ] Microdelivery process established

Issues https://github.com/kyma-project/kyma/issues/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

[janmedrek]

Documentation was recently merged and includes all the architectural and user documentation. Regarding the audit logs - all the operations are executed via the K8S API server, which is already accounted for in the audit logging configuration.