Red Hat 3scale API Management on OpenShift Demo
Last updated
Last updated
Red Hat 3scale API Management on OpenShift Container Platform demonstration preparation and guide.
Backend - represents a deployed backend application or service by pointing to its root URL.
Product - previously called services, represent a collection of 3scale objects that pertain to a specific client or group of users. Products contain the following 3scale configuration objects:
Application plans - sets of access rights that allow users to define different rules for consumers of managed APIs. You can use application plans to set rate limits, enable features, resources, and methods for API users.
Applications - represent a client application who is consuming API(s) via API gateway.
A map of backends to applications
Note that backends do not belong to a product. This is because the same backend can be associated with several different products. Different products do not need separate backends for the same underlying API.
The applictions used for demo are forked from projects created by the clever people out there. All credits are given to the project owners.
Multi-Environments management guideline
API as Code, CI/CD pipeline (Tekton + ArgoCD)
3scale setup using NFS server running in the same cluster
Once you've done all , the overview of OpenShift cluster will be like this.
Follow this for how to test the demo applications.
DO240 - Cloud-native API Administration with Red Hat 3scale API Management course. (, )
