High availability for connecting Kyma runtime with Compass (UCL)

[pbochynski]

Description
Ensure that connection to Unified Customer Landscape (UCL) based on open source project compass can be established regardless of the UCL availability (eventually) also in the bring your own cluster model (BYOC).

Reasons
Currently, the connection between the runtime agent and UCL is initialized by the runtime provisioner. Provisioner connects to the compass director registers runtime and then creates a one-time token as a secret in the runtime. The main disadvantages are:

• in case of UCL unavailability Kyma runtime provisioning fails (even for customers who do not want to use application connectivity)
• Kyma installations on customer own clusters (not proviosioned by Kyma) do not have connection to the UCL (application connector doesn't work there)

High level architecture proposal

The solution introduces a new controller in the contol plane (compass-manager). The controller can watch Kyma resource in the control plane (created for each Kyma installation, also for BYOC model). In the first phase controller will create one-time token for each Kyma cluster. Later on, when application-connector modularization is completed the token can be created only for those clusters where module is enabled.

Current workplan

• Compass Manager - implement registering, and unregistering Runtimes in Compass Director #10
• Compass Manager - implement watching Kyma custom resource #9 - implement action on Kyma CRD deletion
• Compass Manager - Implement creating Secret for Compass Runtime Agent #11
• Compass Manager - prepare migration plan for moving from the architecture based on the Provisioner #12
• Compass Manager - Perform stress test of the Compass Manager #13
• Compass Manager - implement basic e2e tests for Compass Manager #14

[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

[mvshao]

Workplan for Compass Manager

• Prepare the project scaffolding Scaffolding for the Compass-manager #2
• Implement a minimal version of reconciler and watcher for Kyma resource CRD Watching for Kyma Custom Resource #7
• Implement a full version of reconciler and watcher for Kyma resource CRD
• Migrate the application registration logic from Provisioner to Compass Manager

[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

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