Description

Welcome to an exciting demonstration of Gloo Platform Portal's ability to support multiple logical portals, catering to different tenants. In this video, we'll walk you through the process of managing and targeting APIs within these portals.

As you can see, we have two portals deployed in Gloo Platform Portal. The first portal includes two APIs: the Catstronauts API and the Petstore API. On the other hand, the second portal currently doesn't have any APIs deployed. The APIs associated with each portal are selected based on their labels. In this case, we have a "partner dev portal" label and a "dev portal" label.

To showcase the flexibility of Gloo Platform Portal, let's move the Petstore API from one portal to the other. We can achieve this by simply changing the label of the corresponding API product. Once we make the label change, we add it to the Git repository, commit the changes, and push them. Leveraging the power of Argo CD CI/CD pipeline, we apply this update to our Petstore API product.

Upon synchronization with the cluster, we can observe that the Petstore API product has been removed from one portal. Upon refreshing the page, we witness the Petstore API being seamlessly picked up by the other portal, now catering to different tenants and effectively targeting a new audience.

Prepare to be amazed by the versatility and adaptability of Gloo Platform Portal, as it effortlessly handles multiple logical portals, delivering tailored experiences to different tenants. Stay tuned for more powerful demonstrations and transformative features.