Abstract: Presented herein are techniques for orchestrating an update of an on-premises cloud connector from a cloud-based software platform. In particular, a first version of a first cloud connector is running in an active-active configuration across first and second nodes in an on-premises cluster. The first cloud connector is associated with user subscriptions to a first on-premises application and the first cloud connector connects the first on-premises application to a first cloud service hosted at a cloud-based software platform application. The first cloud connector is updated from the first version to a second version on each of the first and second nodes in a sequential manner. The update of the first cloud connector from the first version to the second version is initiated at the cloud-based software platform.

Abstract: Presented herein are zero-downtime upgrade techniques for cloud connector/extension software components. In particular, an on-premises node that runs a first version of a cloud connector software component, receives a second version of the cloud connector software component from a cloud-based software platform. The second version of the cloud connector software component is installed and initialized at the on-premises node such that the first and second versions of the cloud connector software component run in parallel at the on-premises node. Management of the subscriptions of the on-premises services to the cloud-based software platform is then transferred from the first version of the cloud connector software component to the second version of the cloud connector software component.

Abstract: Presented herein are zero-downtime upgrade techniques for cloud connector/extension software components. In particular, an on-premises node that runs a first version of a cloud connector software component, receives a second version of the cloud connector software component from a cloud-based software platform. The second version of the cloud connector software component is installed and initialized at the on-premises node such that the first and second versions of the cloud connector software component run in parallel at the on-premises node. Management of the subscriptions of the on-premises services to the cloud-based software platform is then transferred from the first version of the cloud connector software component to the second version of the cloud connector software component.

Abstract: Presented herein are techniques for orchestrating an update of an on-premises cloud connector from a cloud-based software platform. In particular, a first version of a first cloud connector is running in an active-active configuration across first and second nodes in an on-premises cluster. The first cloud connector is associated with user subscriptions to a first on-premises application and the first cloud connector connects the first on-premises application to a first cloud service hosted at a cloud-based software platform application. The first cloud connector is updated from the first version to a second version on each of the first and second nodes in a sequential manner. The update of the first cloud connector from the first version to the second version is initiated at the cloud-based software platform.