Closed tobiscr closed 4 months ago
Before STAGE and PROD rollout we need to migrate old runtimes that are connected to the Compass and don't have the Application Connector module enabled (creation of the Compass Manager Mapping CRs for already registered runtimes)
depends on #87
@koala7659 as we discussed please let me know if the tasks are done before noon of 10th.Jan. thx.
Compass mgr. onto STAGE: it’s postponed to 18th.Jan.2024 Compass mgr. onto PRODUCTION: it’s postponed to 25th.Jan.2024
Compass mgr. onto STAGE: it’s postponed to 15th.Mar.2024 Compass mgr. onto PRODUCTION: it’s postponed to 22nd.Mar.2024
We detected a problem when after disable integration in Provisioner with Compass to KCP the newly created Kyma Runtime will be missing configuration for Compass Runtime Agent which will cause The Compass Runtime Agent to crash.
To prevent that problem we can combine Compass Manager release with Application Connector module 1.1.0 release. In such a case Compass Runtime Agent will be deployed on Kyma Runtime only when Application Connector is enabled and will be configured correctly. The Rollout plan will contain several new steps.
Compass-manager
is deployed on KCP and registers SKRs in Compass when Application Connector
module is enabledProvisioner
service is deployed to KCP Application Connecto
r module 1.1.0 WITH COMPASS RUNTIME AGENT in Experimental channelProvisioner
overrides to disable integration with Compass
This approach requires to prepare new release of Application Connector first. The module template for fast/regular will have to be applied manually on each separate target environment without submission pipeline It is a problem but also gives us opportunity to remove legacy reconciliator sooner than we planned.
Comment: The migration plan above was discussed and we decided it is too risky as "big bang" approach. Instead of this we will do the rollout in the way we described in main issue
PR with overrides for Dev
@zhoujing2022 Unfortunately we must postpone STAGE delivery again. After we disabled Compass Registration for Provisioner on KCP DEV we discovered that installation of Kyma Runtimes started to fail. We decided to revert the flags, and we must fix Provisioner now. The fix is not a big but we will need at least two days to deliver.
Fix for Provisioner not creating istio-system
namespace when Compass Registration is disabled https://github.com/kyma-project/control-plane/pull/3415
Change request issue for the process [internal github address] /kyma/backlog/issues/5345
Description
To ensure a controlled rollout of the Compass Manager, this cut-over plan is used to define the required steps, their order and owner:
Requires
87
https://github.com/kyma-project/control-plane/issues/3088
More information Please follow the migration plan prepared for the process.
Rollout workplan:
DEV environemnt
STAGE environemnt
PROD environemnt
Stretch: