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

Automated processing of Cloud Provider Health Events

XMLWordPrintable

    • False
    • None
    • False
    • Not Selected

      1. Proposed title of this feature request
      Automated processing of Cloud Provider Health Events

      2. What is the nature and description of the request?
      In AWS (but also other Cloud Provider), there is the concept of health events available, that will notify the consumer of upcoming events, such as instance reboot or similar. Right now, OpenShift Container Platform 4 is not able to process such events. But specifically for components used by OpenShift Container Platform 4 (such as instances) it would be nice if those health events could be processed and instances scheduled for reboot could be replaced beforehand to minimize disruption.

      One example could be, to set the affected instance to scheduling disabled, create a new OpenShift Container Platform 4 - Node and then drain the affected OpenShift Container Platform 4 - Node. Certainly this is not the only option but a simple idea to help understand what is being requested to process such Events.

      Also View scheduled events contains an example of such an event.

      While the above is an example, it's key that it should not be limited to this idea. Another approach could also be to capture the event and make it available to end-user via Console or Alert to at least be aware of what is happening and allow customers to trigger their own automation or have the knowledge of what is going to happen.

      3. Why does the customer need this? (List the business requirements here)
      Even though, application running on OpenShift Container Platform 4 are robust and can deal with potential loss of OpenShift Container Platform 4 - Node, it would be appreciated if this could be handled more graceful (at least information about the cloud provider notification). Currently the OpenShift Container Platform 4 - Node is just rebooted based on AWS schedule while actually, it could be done in a more controlled manner. That way, SRE would also better understand why a given OpenShift Container Platform 4 - Node restarting and not require potential troubleshooting

      4. List any affected packages or components.
      OpenShift Container Platform 4

      • AWS
      • Azure
      • GCP
      • Alibaba

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

              Created:
              Updated: