TODO rewrite this for OCP 4.x - probably just force this to be part of Service Mesh install
The latest official install guide can be found here: TBD.
Note that if you are using Istio too, you can leverage the 3scale adapter by following instructions here.
The simple version is:
- Update the environment variables in 3scale-install.sh with the appropriate values. The OCP_ROUTE variable should be set to the wildcard domain of your cluster
- Make sure you are
oc login-ed as a cluster admin - Run ./3scale-install.sh
- This will install an on-premise version of 3scale. The install will also update the openshift router to enable wildcard routing. More information can be found here. With wildcard routing enabled, you don't have to manually create openshift routes for every API 3scale manages
- Make sure you save all the credentials that were generated by the install
Alternate version:
- To use the 3scale SaaS API Manager, sign up at 3scale.net
- The SaaS version includes an API gateway and that can be leveraged. However, ideally the API gateway should be running in the same cluster as your microservices
- Make sure you are
oc login-ed - Update the environment variables in 3scale-gateway-install.sh with the appropriate values. Retrieve the Access Token from Get the Access Token from Settings Widget->Personal->Tokens
- Run ./3scale-gateway-install.sh
- If your cluster allows wildcard routing or you have cluser admin rights to enable wildcard routing, comment out the commands in 3scale-gateway-install.sh to install the wildcard router.
- If your cluster doesn't allow wildcard routing, create individual routes for the APIs being managed.
- Make sure you are