Compass Manager uses KCP Sync Resource to create compass-agent-configuration on SKRs

[mvshao]

Description

Compass Manager should not create separate Kubernetes clients for each SKR, but use a solution to be provided by the lifecycle-manager. That solution will enable central synchronisation and k8s resource creation on client clusters. Information on progress as well as architectural decisions can be found in this ADR.

Additional information

For the first release of Compass Manager, we will not use this approach because it has not yet been implemented. Eventually, we will dispose of our own Kubernetes client for SKR, and replace it with the central approach proposed in ADR (mentioned above)

[ruanxin]

Hi @mvshao,

Can you describe the resources you plan to use this Sync Resource to sync with? And what is the expected input data to generate your resources? Is the resources' content dynamic for each SKR or identical? I'm currently trying to collect all the usages for this Sync Resources. Thanks! Also feel free directly reach me in slack.

Best,
Xin

[mvshao]

Hi @ruanxin,
In the future when this resource is added we plan to use it for upserting compass-agent-configuration Secret on SKR. The expected data contains an authorization Token for Compass Director and 2 different fields that identify Runtime in Compass. The values in Secret are different for every SKR and for different environments (DEV/STAGE/PROD).

[tobiscr]

@mvshao : is this a feature for the compass manager or related to LCM (probably related to this one: kyma-project/lifecycle-manager#913)?

Not sure how this issue should be classified.. is it a feature request for CM which could be implemented after the LCM offer remote synchroized resources?