Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KIM:add mechanism to prevent incompatible migration of Shoot-Spec #400

Open
1 task
tobiscr opened this issue Sep 26, 2024 · 0 comments
Open
1 task

KIM:add mechanism to prevent incompatible migration of Shoot-Spec #400

tobiscr opened this issue Sep 26, 2024 · 0 comments
Assignees
Labels
area/control-plane Related to all activities around Kyma Control Plane kind/feature Categorizes issue or PR as related to a new feature.

Comments

@tobiscr
Copy link
Contributor

tobiscr commented Sep 26, 2024

Description

To block critical changes in already published Shoot-CRs, KIM was to be extended to detect critical changes it would apply in the Shoot-CR during the migration.

KIM is only allowed to migrate an existing SKR Shoot-CR if its generated Shoot-CR looks not different compared to the existing Shoot-Spec.

Incompatible changes will be detected and reported via either Metrics to the operational team or/and written to KIM logs.

Screenshot 2024-09-26 at 11 22 47

AC:

  • KIM is able to detect incompatible changes in the Shoot-Spec before it's updating the Shoot-Spec on Gardener's Seed. cluster.

Reasons

Prevent incompatible Shoot-Spec changes to prevent service interruptions by KIM.

Attachments

@tobiscr tobiscr added kind/feature Categorizes issue or PR as related to a new feature. area/control-plane Related to all activities around Kyma Control Plane labels Sep 26, 2024
@Disper Disper removed their assignment Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/control-plane Related to all activities around Kyma Control Plane kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

4 participants