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

After Go-Live: KIM becomes the default reconciliation system and reacts on CRs which have no "controlled-by" label #297

Open
1 task
tobiscr opened this issue Jul 16, 2024 · 0 comments
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 Jul 16, 2024

Description

At the moment, we configured KIM to behave defensive and consider on CRs which have the label set kyma-project.io/controlled-by-provisioner: false which clearly indicates taht KIM has to reconciler the cluster (see #250). If the label is missing, KIM is ignoring the CR.

After KIM's go live, we will change this behaviour and KIM has to reconcile has to reconcile the cluster if

  1. the label is missing on the CR
  2. the label indicates that KIM has to reconcile the cluster

AC:

  • KIM behaves "aggressive" and reconciles also clusters without the label kyma-project.io/controlled-by-provisioner or when the label indicates that KIM has to reconcile them

Reasons

KIM has to become the default cluster reconciliation system and will manage also clusters with are not explicitly defining KIm as the reconciling system via labels.

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 Jul 16, 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

1 participant