• No-CNI support on cluster creation
    • False
    • Hide

      None

      Show
      None
    • False
    • To Do

      Feature Overview (aka. Goal Summary)  

      An elevator pitch (value statement) that describes the Feature in a clear, concise way.  Complete during New status.

      Support no-cni on CREATE CLUSTER of ROSA with HCP.

      XCMSTRAT-358 is the feature that introduces in API/ CLI.  

      Goals (aka. expected user outcomes)

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

      1. OCM UI parity for ROSA with HCP features

      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.

      Supported Clients Option
      Supported in ROSA cli ( ) Yes ( x) No ( ) N/A
      Supported in OCM cli ( ) Yes ( x) No ( ) N/A
      Supported in OCM UI (x ) Yes ( ) No ( ) N/A
      Supported in TF () Yes No ( ) N/A
      Supported in Capi ( ) Yes ( ) No ( ) N/A
      Supported Offerings Option
      Fedramp supported? ( ) Yes ( ) No N/A
      OCP Support Option
      Is it already supported in OCP? ( x) Yes ( ) No ( ) N/A
             If Yes, what OCP version ?  

       

      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
              rh-ee-bchandra Balachandran Chandrasekaran
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: