search

kyma-project / kyma-environment-broker

Kyma Environment Broker
Apache License 2.0
0 stars 21 forks source link

KIM integration - deprovisioning step chooses KIM or provisioner #1147

Closed jaroslaw-pieszka closed 1 week ago

jaroslaw-pieszka commented 2 weeks ago

Deprovisioning behaviour should depend on existence of Runtime CR and label setting not on plan settings.

Currently we use either KIM or provisioner inferring from the plan which path we should use: provisioner call, or Runtime CR removal.

If Runtime CR exists and contains label "kyma-project.io/controlled-by-provisioner": false we should not call provisioner. Otherwise we call provisioner to deprovision.

We always remove Runtime CR if exists.