Business Problem:

When a customer adds the SecuredCluster to an EKS deployment that need to generate a service account in OCM and use the password and naming there to create a secret. It's not hard per se, but it's clunky and, in our experience in the lab we did at Red Hat Summit 2024, caused a lot of frustrations for customers. If one part of that secret creation fails it through folks into a lot of confusion. 

The general response was to ask why all that was needed and could it be easier "like adding a SecureServer for OpenShift is."

Use Cases:

When customers would like to add non-OCP cluster to ACS as a SecuredCluster to EKS and other non-OCP clusters allowing for true multi-cloud management.

Key Functionality:

Allows EKS, AKS, GKE, etc to be more easily managed.

Benefits:

Allows EKS, AKS, GKE, etc to be more easily managed.

Acceptance criteria:

Avoid the multi-step, cut and paste process to enable Secured Clusters on non-OCP instances.

Implementation Suggestions (optional):

N/A

Timeline:

Not urgent, but will make first touch on the product a better experience for non-OCP environments, which is very important.

Please use the following Jira fields to complete this Feature Request

1. [Jira Field] Summary Required: [Provide a clear and concise name/description for the feature]
2. [Jira Field] Description:
3. [Jira Field] Component:
4. [Jira Field] Priority: [Indicate the importance or urgency of the feature on a scale of High, Medium, or Low]

1. [Jira Field] Supporting Documentation:
    

1. [Attach any relevant documents, research, or supporting materials that provide additional context or information]