Rollback 8.5 High availability and scaling on containers for API  Management 8.5.1 High availability in a containerized environment 552  Accelerating Modernization with Agile Integration API Connect leverages Kubernetes as a container orchestration platform and also the  Quorum concept (described in “Quorum” on page 554) to provide a sophisticated high  As discussed in the introductory chapters, agile practices in integration are giving rise to new  patterns of deployment. We need the API management infrastructure to be able to fully use  the cloud-native infrastructure, both from a high availability point of view and also to enable  scaling. In this section, we explore how deployment on containers enables API Connect to  provide a more nuanced availability and scalability model. This uses the underlying  standards-based Kubernetes platform to look after the infrastructure orchestration, simplifying  installation and maintenance of the overall topology. The guideline provided for automation shows that REST APIs are available on the API  Connect Cloud in order to sufficiently automate the provisioning of API Provider teams.  Individual use cases might vary and the assembly of the different REST APIs into a process  need customization into some form of pipeline. In the event of a rollback, there are two options available. The first option is to use backup  configurations of the system to bring the system back to before the changes were made.  However, this risks losing API, product, and membership data, which would be a  heavy-handed approach. The second option is a fix forward strategy. This can be achieved by using the available  REST APIs to GET all the relevant resources that might be touched by the automation or  manual process. Given an event that requires a rollback, the system can be restored to its  previous configuration (active Organizations and Catalogs). You can use either a manual  process or further automation that resolves the configuration to a pre-change state. We can now provision new API Provider teams using both manual and automated steps in  API Connect. a. Gateway Services need to be deployed independently using the subsystem definitions for the gateway leveraging  the apicup installer, requiring specific editing of namespace and image registry. This can then be deployed ready  for automated addition to the API Connect Cloud as above 10 Set up Developer Portal (If  applicable) 10a Enable and configure  Developer Portal with validation PUT /catalogs/{org}/{catalog}/settings 10b Set up admin user and add  relevant members to the portal New Consumer Organizations can be set up to host API Provider users in  the new Portal: Create an Org: POST /consumer-api/orgs Invite new users: POST consumer-api/orgs/{org}/member-invitations POST consumer-api/orgs/{org}/members Step Task Automation