Feature Overview (aka. Goal Summary)  

RHOIC clusters are currently registered with OCM when they send telemetry. However, since these clusters are not provisioned by OCM, they are not specifically recognized as RHOIC and instead registered as OCP clusters.

This feature request is to correctly recognize RHOIC clusters in OCM based on the appropriate telemetry metric/label. Also, we need to allow the transfer of existing RHOIC clusters from the IBM organization to the customer's RH organization.

Goals (aka. expected user outcomes)

There is an effort to allow RHOIC customers to see their clusters in OCM by allowing them to provide their own pull secrets for these clusters - either as a day-1 operation or as a day-2 operation. Once we move ahead with that, we would want to list these clusters correctly as RHOIC instead of OCP.

Requirements (aka. Acceptance Criteria):

• Look at telemetry metric/labels for OCP clusters being registered and if telemetry has the RHOIC-specific metric/label, then set the product/plan to RHOIC
  • metric: cluster_infrastructure_provider
  • label: type="IBMCloud"
  • alternate label: service="roks-metrics"
  • See these clusters in prometheus --> cluster_infrastructure_provider{type="IBMCloud", service="roks-metrics"}
• This is similar to what is being done for ARO and the same process should apply
• The same cluster detail screens that show up in the OCM console for ARO should be enabled for RHOIC clusters as well.
  • Cluster list: Include RHOIC in the list of filters for product types.
  • Overview tab: display same attributes as ARO
  • Access Control: display the OCM roles and access section - same as ARO
  • Cluster History: same as ARO
  • Support: Display only the notification contacts section and hide the Support case creation section for now. This is because customers will not receive support for RHOIC clusters through Red Hat, they will not be able to open up support cases through OCM
• Allow cluster owners and org admins to initiate cluster ownership transfer of RHOIC clusters, similar to the functionality that exists for OCP clusters.
  • IBM will initiate the cluster ownership transfer of these clusters since these are currently in the IBM organization
  • The clusters will get transfered to the customer's RH organization once the pull secrets are updated

Use Cases (Optional):

Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

Questions to Answer (Optional):

Include a list of refinement / architectural questions that may need to be answered before coding can begin.  Initial completion during Refinement status.

Out of Scope

A subscription for the RHOIC SKU will not be created for the customer account because customers will not receive support for RHOIC clusters through Red Hat. They will not be able to open up support cases through OCM for their RHOIC clusters.

Background

We already have a process where we initially create a cluster (subscription) record in OCM as an OCP cluster and then look up telemetry to switch it to ARO if the appropriate telemetry metrics are present.

We need to do the same thing for RHOIC as well. RHOIC clusters will be mostly view-only in OCM, similar to ARO and the cluster detail tabs visible in OCM for ARO should be the same ones that apply to RHOIC clusters.

Customer Considerations

Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

Documentation Considerations

Provide information that needs to be considered and planned so that documentation will meet customer needs.  Initial completion during Refinement status.

Interoperability Considerations

Which other projects and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.