Service Registry integration

[wtrocki]

Integrate with Service Registry Service following the same design as currently available Kafka integration.

Steps

0. Service registry support in Operator: RegistryConnection CR is part of the Operator.
1. Add a new title icon to the catalog (Add Flow)
2. Add Table presenting registry list
3. Add Support for Topology

Technical details

Add flow

To start with the creation of the service registry we need to provide new tile in catalog of Managed Services.
This can be done by adding new item to the catalog content array:
https://github.com/redhat-developer/app-services-openshift-console-plugin/blob/main/frontend/packages/rhoas-plugin/src/catalog/catalog-content.ts

Example: #169

Once we have catalog content done we need to create new route/type for service registry:
https://github.com/redhat-developer/app-services-openshift-console-plugin/blob/main/frontend/packages/rhoas-plugin/src/plugin.ts#L29-L44

We can either:

• Choose to reuse existing Kafka UI and share it with service registry (some of the columns will not be required and will need to be disabled)
• Naively copy paste code for service registry and adapt it.

When Service registry will be integrated into Operator CloudServicesRequest will return extra field in status:

registries: []

This field will contain all registries that user has and that can be populated into the view.

Operator should also provide RegistryConnection resource that should have the same logic as KafkaConnection.

Topology integration

Review ./topology folder of the plugin and duplicate logic we have for Kafka to map RegistryConnection CR.
There might be more clever way to integrate this in future.
Please seek help and advice of the OpenShift Console Team

Design:

[Final design] Red Hat OpenShift Streams for Apache Kafka experience.pdf

Blocked by

• Service Registry Integration  app-services-operator#217