Support migration of "old style" Kyma component to Connectivity Proxy module [EPIC]

[tobiscr]

Description

As final step of the Kyma modularisation, the Connectivity Proxy component has to be migrated to a modularised solution.

We are supporting the CP team during the migration by taking over following tasks:

• [x] #18451
• [x] Support root-cause analysis of last CP upgrade (#sap-github/backlog/4907)
  • [x] Update customer incident issue with description of the root cause
• [x] Investigate what needs to be done to allow the Connectivity Proxy module to be deployed in kyma-system (Warden)
• [x] #18528
  • [x] Come up with check-list for CP team to ensure nothing get's forgotten
• [x] #18482
• [x] #18521
• [ ] Setup a post mortem call with FF and CP team + @arturskorupa and @zhoujing2022 to verify how good the guidance and support during the module development was

[akgalwas]

Here is the list of functionalities that are required for the module to fully integrate with Kyma:

• [x] Creating, TLS certificate for business tunnel. External business tunnel URL must be built in the same form as the old Connectivity Proxy Reconciler does (cp.[cluster domain]) to avoid breaking existing installations. The certificate should be renewed before it expires In progress
• [x] The UI exposes only the CRD properties that the user can modify (e.g. everything under spec.deployment key is not visible). TODO
• [x] Operator sets defaults for the CR values that should not be set by the user (deployment section). In progress Note: final solution not decided yet.
• [x] Operator reacts on changes in CR values and modify managed Connectivity Proxy application state accordingly.
• [x] The state of the module installation should be reflected correctly in CR status section
• [ ] Operator should expose metrics on its functionality that are integrated with Grafana in KCP
• [x] Integration with the BTP Operator. In progress
• [x] Operator should not override existing user configuration during module upgrade
• [x] For existing installations the module must be able to take over existing Service Mappings

Additional requirements:

• [x] If the external dependency is not available the operator should not apply resources. If the external dependency is enabled the module resources must be applied.
  • [x] The operator should make sure that Istio required CRDs such as VirtualService are available and wait for installation in "Warning" state until Istio is available. If Istio CRDs are missing meaningful status should be set in the CR.
  • [x] The operator should make sure that BTP related CRDs are available (serviceinstance.services.cloud.sap.com, and servicebinding.services.cloud.sap.com). If BTP Operator is not available meaningful status should be set in the CR.

[zhoujing2022]

• UI is under tests.
• Monitoring for metrics will be done before Golive.

[Disper]

Setup a post mortem call with FF and CP team + @arturskorupa and @zhoujing2022 to verify how good the guidance and support during the module development was

We can help and share our observations but we're no longer leading the topic