Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-6718

ROSA HCP Cluster fails to notify autoscaling events or failures

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • Product / Portfolio Work
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      1. Proposed title of this feature request
        1. ROSA HCP Autoscaling and Quota Notifications
      2.  What is the nature and description of the request?
        1. Feature Overview (aka. Goal Summary)  

      Allow appropriate intelligence between Autoscaling functions with HCP and AWS Quota limits

      Goals (aka. expected user outcomes)

      1. Allow customers to receive appropriate notifications when AWS Quota limits impact autoscaling strategies
      2. Allow customers to take appropriate actions to navigate the AWS Quota limits

         

      1.  Why does the customer need this? (List the business requirements here)

      Requirements (aka. Acceptance Criteria):

      • Support for ROSA HCP
      • When the customer nears the AWS Quota limit, a notification is raised explaining the potential impact and how to navigate how it may impact the established autoscaling strategy.
        • As a cluster administrator, there should be an obvious alert in the admin console UI that autoscaling events are unsuccessful. Since the control plane is not in the customer account, they don't have any observability into these types of events unless we give it to them.
        • When the customer reaches the AWS Quota limit, a notification is raised explaining the impact and how to navigate how it impacts the established autoscaling strategy.

           

      Use Cases (Optional):

        1. Customer is vigilant in managing their costs and quotas.  The customer was unable to autoscale, and it was not clear why.  After digging, it was identified that they had reached the quota limit.  This causes concern and workarounds to be considered to prevent production impact.

           

      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.

      • The customer is currently using ROSA with HCP and is having difficulties with autoscaling and visibility into its challenges, such as reaching the quota limit.  

      Customer Considerations

      • The customer is scaling across multiple regions and AZs.  This visibility is essential for how they do resource management and allocation as well as passthrough costs. 

      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.

      .

              rh-ee-bchandra Balachandran Chandrasekaran
              jfaett@redhat.com Jesse Faett
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                None
                None