Goal Summary:

In 4.7 we introduced Cluster Registration Secret(CRS) as a means to securely bootstrap Secured cluster registration with RHACS Central. Unlike the previous initBundle functionality, CRS provides clear separation of credentials used for bootstraping registration of Secured cluster components from the workflow of internal communication between these components. 

With support in UI as well as CLI, and having reviewed usage in last 3 releases, we are now ready to make this feature Generally available. We are looking to make CRS the default method for registration of Secured cluster and we look to deprecate initBundle usage in a future release. 

Goals and expected user outcomes:

Make CRS the recommended choice for secured cluster registration via UI. 

Remove any TechPreview verbiage 

Provide deprecation notice for initBundle

Acceptance Criteria:

UI clearly shows CRS as recommended way to register Secured clusters with Central

Customers attempting to register/add new Secured clusters into Central can use CRS without any problem

In case of upgrades, Clusters that are already registered with initBundle dont have any impact and only for new clusters are recommended to connect using CRS

Success Criteria or KPIs measured:

Use of CRS as default method for adding Secured clusters

No disruption to existing clusters added with initBundle

Use Cases (Optional):

Include use case diagrams, main success scenarios, alternative flow scenarios together with user type/persona. Initial completion during Refinement status.

<your text here>

Out of Scope (Optional):

High-level list of items that are out of scope. Initial completion during Refinement status.

<your text here>