• Icon: Feature Feature
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Core, Lifecycle, Multicluster
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • OCPSTRAT-764[Outcome] Leverage Cluster API to introduce new features to OpenShift
    • 0% To Do, 0% In Progress, 100% Done
    • 0
    • 0

      Feature Overview (aka. Goal Summary)  

       

      Customers would like to have the ability to CRUD OpenShift Managed Services clusters (including ROSA, ARO and OSD) via CAPI (https://github.com/kubernetes-sigs/cluster-api) They would like to use CAPI as a part of automation (Infra as Code)  tool chain that can CRUD Kube clusters. 

      Goals (aka. expected user outcomes)

      The observable functionality that the user now has as a result of receiving this feature. Complete during New status.

       

      As a user, I am running my own CAPI service and I want to expose this end point to my end users to CRUD ROSA, ARO and OSD clusters 

      Requirements (aka. Acceptance Criteria):

      A list of specific needs or objectives that a feature must deliver in order to be considered complete.  Be sure to include nonfunctional requirements such as security, reliability, performance, maintainability, scalability, usability, etc.  Initial completion during Refinement status.

       

      Create a CAPI plugin for OCM. 

      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

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

       

      Background

      Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

       

      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.

            Unassigned Unassigned
            tkatarki@redhat.com Tushar Katarki
            Abhishek Gupta, Adel Zaalouk, Jerome Boutaud, Joel Speed, Mike Barrett, Subin MM
            Derek Carr Derek Carr
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: