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

Support for AWS Placement Group Partition Number

XMLWordPrintable

    • False
    • None
    • False
    • Not Selected

      1. Proposed title of this feature request
      Support for AWS Placement Group Partition Number

      2. What is the nature and description of the request?
      Based on RFE-2194, support for pre-created Placement Groups was added in OpenShift Container Platform 4.14. Following that, it was requested to also have the ability to specify the Partition Number of the Placement Group as this allows more precise allocation (specifically in AWS Outpost).

      For details see Partition placement groups and Placement - API Reference where it can be see that the Partition Number can be defined on EC2 level.

      Placement Group and Partition Number are again pre-created and don't need to be created or maintained by OpenShift Container Platform 4. Yet specifying Partition Number in MachineSet along the PlacementGroupName would be appreciated to improve availability further.

      3. Why does the customer need this? (List the business requirements here)
      Specifically when running OpenShift Container Platform 4 on AWS Outpost (as per Installing a cluster on AWS with remote workers on AWS Outposts, it's required to configure high availability using Placement Groups. Given that Placement Groups have different ways to be implemented, it was found that Partition Numbers are the most suitable approach to achieve highest level of availability, which is why it was requested to add support for Placement Group Partition to OpenShift Container Platform 4.

      4. List any affected packages or components.
      cluster-api-provider-aws

            rh-ee-smodeel Subin M
            rhn-support-sreber Simon Reber
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: