BTP Manager - unified service management and new UI

[PK85]

Description

The BTP Manager component broadens the btp-operator module features set. Right now, it enables SAP BTP Service Operator almost 1:1 with some out of the box configurations and credentials. Next step is to support Unified Service Management in the Kyma cluster, which means:

1. has own UI which uses Secrets (Same secrets that SAP BTP Service Operator work with) and then uses REST APIs that proxies calls to Service Manager. We aim to be embedded into Busola dashboard with authorization rule: "U have access to secret you can manage instances and bindings"
2. doesn't work only with k8s resources but execute calls to Service Manager directly. The k8s Secret with credentials to given service is created and ready to be used by Applications.

Technical Acceptance Criteria

• [ ] 1) BTP Operator UI embedded in the Busola Dashboard, see: https://github.com/kyma-project/busola/issues/3122
• [ ] 2) Authentication and Authorization is defined and works from Busola to BTP Operator UI and REST APIs

Business Acceptance Criteria

• [x] 1) User wants to have only k8s secret in the given namespace with credentials to given Service, see POC
• [ ] 2) User wants to see Service Marketplace in the Kyma cluster
  • [ ] 2.1) Improve existing Service Management View or create a new ones to show offerings to the user
• [ ] 3) User wants to restore Service Manager instances into Kyma cluster
• [ ] 4) Users want to login to BTP, and create Service Instances in a "User" mode. Description: User creates SM instance with "btp-operator-access" plan in the given SA for service instance sharing purpose.

Other rejected Acceptance Criteria

• [ ] 1) User wants to setup automatic Secret rotation:
  • [ ] 1.1) Rotate existing secret
  • [ ] 1.2) Rotate existing secret and kick workloads (required by some some apps)
• [ ] 2) User wants to see how many CLUSTER_IDs where used for service instance creations for given secret.
• [ ] 3) Users wants to work with/check sharable instances and use "reference-instances" plan

[PK85]

After discussion (6.08.2024) with PB:

• [ ] 1) check SAP BTP Service Operator when user creates SI, SB (Secret to) is that created by user or operator Service Account?
• [ ] 2) We decided to not go and support SI,and SB creation directly and only via Service Manager. We want first to focus showing service offering in the UI in the existing views.
• [ ] 3) We decided to base on SI and SB creations by SAP BTP Service Operator, and give some additional features and options like:
  • [ ] 3.1) catalog offering per calculated secret - helps to create SI without a need to go to BTP cockpit
  • [ ] 3.2) help user to create reference instance to the shared instance from different Subaccount - here login to BTP as user will be required get shared instance ID, create btp operator access instance and create secret in the Kyma Runtime.
  • [ ] 3.3) Service Binding data format and rotations will be used from SAP BTP service operator, we do not need to impement them
  • [ ] 3.4) We support overview of other instances(different clusterID) from given secret. The SAP BTP Service Operator works only with the one given cluster ID, our UI will be able to list all instances and bindings for information purpose.
  • [ ] 3.5) If any issues occur in the k8s cluster, e.g. namespace deletion with stuck Instances/Bindings, user will be able to recover from such states. Direct calls to SM to delete/update will be possible.