Move Compass Runtime Agent to the new Kyma modular architecture

[janmedrek]

Description

According to this concept concept we move towards modular architecture. Compass Runtime Agent will be an apart of Application Connector module. The architecture of the Kyma Control plane will be changed, and there will be a new component introduced called Compass Manager.

Reasons

Provisioner component that is responsible for registering Runtimes will be replaced by Provisioning Operator. The Provisioning Operator will no longer register Runtimes so that new component needs to be introduced.

Acceptance Criteria

• Compass Manager must register Runtimes in Compass Director
• Compass Manager must obtain One Time Token and create configuration secret for Compass Runtime Agent
• Compass Manager must detect that Application Connector module is installed in the Runtime
• Documentation prepared

[akgalwas]

Steps.

1. Prepare POC for using Runtime Watcher for detecting Application Connector module (8). Scope:
   • Prepare initial project structure with pipelines. Create new repository in github.com/kyma-project.
   • Define what resources should be observed (Kyma CRs?)
   • Create operator with Kubebuilder
   • Use Runtime watcher to get notifications from the Runtime watcher. Detect that module is installed and print information to the log.
2. Productise the POC (5)
   • Implement registering Runtimes in Compass
   • Implement getting One Time Token and pushing Compass Runtime Agent configuration to the Runtime
3. Consider preparing integration test (8)

[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:

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

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[Disper]

Duplicated by kyma-project/compass-manager#107.