search

SAP / sap-btp-service-operator

SAP BTP service operator enables developers to connect Kubernetes clusters to SAP BTP accounts and to consume SAP BTP services within the clusters by using Kubernetes native tools.
Apache License 2.0
126 stars 52 forks source link

ServiceBindings in CreateInPrgress state deleted from k8s cluster but doesnt reflect the same deleting in btp-cockpit #426

Closed krimeshshah closed 6 months ago

krimeshshah commented 7 months ago

Hi Team,

Following this issue (https://github.com/SAP/sap-btp-service-operator/issues/417) we faced few weeks back, we tried reproduce the scenario in our test cluster.

Test Scenario1.

  1. Created xsuaa service instance with exsiting clusterid in btp-operator
  2. Changed the cluster id
  3. Created service binding successfully (created with running state)
  4. Triggered credential rotation to trigger service binding rotation
  5. Newly created service binding was in Updated and ready state

Test Scenario 2: From Test Scenario 1, step 1 to 3 performed as it is

  1. Changed the cluster ID again after creation of servicebinding
  2. Triggered the credential rotation
  3. Which caused newly created service binding in CreateInProgress state

Observation and a problem here was, even though the service binding was in CreateInProgress state in k8s cluster, the corresponding service binding in btp-cockpit was in running state. Also when we deleted the ServiceBinding from k8s cluster, it did not reflect and delete it in btp-cockpit. Can you please check and provide solution to this.

kerenlahav commented 7 months ago

Hi @krimeshshah Changing the cluster id is not a valid use case and is not supported, a cluster id validation was added in release v0.6.2, in case changed the operator will not be able to start please use the latest version. Thanks

kerenlahav commented 6 months ago

closing since there is no comment, please reopen in case needed