MVP: Module Manager

[tobiscr]

Description

The Module Manager is part of the new reconciler architecture. It is following the K8s operator pattern reacting on data changes (defined in CRs).

A Module Manager is responsible for the lifecycle management of a Kyma module. It is behaving idempotent and determines whether a Kyma module has to be installed, updated or deleted on Kubernetes cluster. If necessary, it applies migration steps if a component update requires enhanced adjustments on Kubernetes side (e.g. data migrations, cleanup of resources etc.).

A Module Manager can be responsible for the reconciliation of one or multiple Kyma modules, but a Kyma module itself is always processed by only one Module Manager at the same time.

The MVP includes a reference implementation of a simple Module Manager which is capable to reconcile a common Helm chart.

Acceptance criteria General ACs:

• [x] #4
• [x] #40
• [x] #41
• [x] Caching of rendered manifests
• [x] https://github.com/kyma-project/manifest-operator/issues/38
• [x] #45
• [ ] Documentation
  • [ ] Architectural design documentation available
  • [x] #143
• [x] A strategy is defined, how a Module Manager can be scaled (e.g. via sharding or following an active-passive cluster-mode pattern etc.)
• [ ] Operational requirements are covered
  • [ ] For debugging purposes are component-IDs injected into each log message (to correlate messages per component CR)
  • [ ] Exposing analysis and statistic relevant data via Prometheus endpoint
  • [ ] Logging of critical events
  • [ ] Operational test was executed and trouble-shooting guides were created
• [x] Support local and remote reconciliation strategy
• [x] Threat modelling findings implemented (see https://github.com/kyma-project/lifecycle-manager/issues/144)
  • [x] https://github.com/kyma-project/lifecycle-manager/issues/151
• [ ] Microdelivery process established
• [x] Cleanup for manifest and CRs

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

[kyma-bot]

This issue or PR has been automatically closed due to the lack of 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:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle stale

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

/close

[kyma-bot]

@kyma-bot: Closing this issue.

In response to [this](https://github.com/kyma-project/module-manager/issues/3#issuecomment-1369682934): >This issue or PR has been automatically closed due to the lack of 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: >- Reopen this issue or PR with `/reopen` >- Mark this issue or PR as fresh with `/remove-lifecycle stale` > >If you think that I work incorrectly, kindly [raise an issue](https://github.com/kyma-project/test-infra/issues/new/choose) with the problem. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[jakobmoellerdev]

/reopen /remove-lifecycle stale

[kyma-bot]

@jakobmoellersap: Reopened this issue.

In response to [this](https://github.com/kyma-project/module-manager/issues/3#issuecomment-1369683791): >/reopen >/remove-lifecycle stale Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.