How to clean up a namespace with service instance & bindings properly with helm?

[sim-lus]

We are running on Kyma using github action pipelines with piper.
Our yaml chart contains sth. like this:

apiVersion: services.cloud.sap.com/v1
kind: ServiceInstance
metadata:
  name: {{ .Values.btpservice.destination.name }}-{{ .Release.Namespace }}
  namespace: {{ .Release.Namespace }}
spec:
  serviceOfferingName: {{ .Values.btpservice.destination.name }}
  servicePlanName: {{ .Values.btpservice.destination.planname }}
---
apiVersion: services.cloud.sap.com/v1
kind: ServiceBinding
metadata:
  name: {{ .Values.btpservice.destination.name }}-{{ .Release.Namespace }}
  namespace: {{ .Release.Namespace }}
spec:
  serviceInstanceName: {{ .Values.btpservice.destination.name }}-{{ .Release.Namespace }}
  serviceInstanceNamespace: {{ .Release.Namespace }}
  secretName: {{ .Values.btpservice.destination.name }}-{{ .Release.Namespace }}
---

We are uninstall it in our piper script via:

helm uninstall namespace-config --kube-context rcdev --namespace ns-test --wait --timeout 300s

Afterwards we are deleting the namespace in the script.

Sometimes one of the following two issues occur:

1. The uninstall-command run into the 300s timeout: In the cluster everything is gone then, however in the BTP cockpit the instance (without the bindings) are still present
2. The instance and secrets are gone, but the binding remains in the cluster, keeping the namespace in "Terminating"-state. In BTP cockpit both still exist.

How to solve this properly for both cases?

Issue 2 is I guess somehow an order problem, how can helm handle this correctly?
To get out of issue 1 I found some documentation, but how to avoid it at all?

[I065450]

Hi @sim-lus

The recommended way to delete a namespace is to manually delete all associated service instances and bindings beforehand. This ensures that all data stored with service instances and bindings is properly handled.

Instances and bindings that are not manually deleted will be automatically removed during the uninstallation process.
This process first deletes bindings, and if a single binding fails or takes too long, the entire process may fail.

https://github.com/SAP/sap-btp-service-operator?tab=readme-ov-file#uninstalling-the-sap-btp-service-operator

Regards,
Naama

[sim-lus]

What exactly do you mean by manually deletion? Running kubectl on each of the entities? Or deletion via kyma dashboard?

While having automated deployments and pipelines, doing some manual task is not feasible.

BTW I don't want to uninstall the service operator, but rather cleanup a dedicated namespace with the service instance and bindings in it.

[I065450]

Both options work well for manual deletion.
If you rely on the automated process, there are issues with it, as you mentioned.

Regards,
Naama

[sim-lus]

We try to incorporate these two steps into our scripts separately now in the hope to prevent this.

It would be nice to have at least some dedicated documentation for this.