1. By default you are logged in as developer and can proceed to the next step.

   Otherwise login into OpenShift using the oc login command from the OpenShift Client tools you downloaded and installed in the previous step. The default login credentials are username = "developer" and password = "developer":

   oc login https://OPENSHIFT-SERVER-IP:8443

   You should see Login successful. in the output.

2. Create your project. This example sets the display name as gateway

   oc new-project "3scalegateway" --display-name="gateway" --description="3scale gateway demo"

   The response should look like this:

   Now using project "3scalegateway" on server "https://172.30.0.112:8443".

   Ignore the suggested next steps in the text output at the command prompt and proceed to the next step below.

3. Create a new secret to reference your project by replacing <access_token> and <domain> with your own credentials. See below for more information about the <access_token> and <domain>.

   oc create secret generic apicast-configuration-url-secret --from-literal=password=https://<access_token>@<admin_portal_domain>  --type=kubernetes.io/basic-auth

   Here <access_token> is an Access Token (not a Service Token) for the 3scale Account Management API, and <domain>-admin.3scale.net is the URL of your 3scale Admin Portal.

   The response should look like this:

   secret/apicast-configuration-url-secret

4. Create an application for your APIcast gateway from the template, and start the deployment:

   oc new-app -f https://raw.githubusercontent.com/3scale/3scale-amp-openshift-templates/{ThreescaleVersionGA}/apicast-gateway/apicast.yml

   You should see the following messages at the bottom of the output:

   --> Creating resources with label app=3scale-gateway ...
       deploymentconfig "apicast" created
       service "apicast" created
   --> Success
       Run 'oc status' to view your app.

1. Open the web console for your OpenShift cluster in your browser: https://OPENSHIFT-SERVER-IP:8443/console/

   Use the value specified in --public-hostname instead of OPENSHIFT-SERVER-IP if you started OpenShift cluster on a remote server.

   You should see the login screen:

   
   Note

   You may receive a warning about an untrusted web-site. This is expected, as you are trying to access the web console through secure protocol, without having configured a valid certificate. While you should avoid this in production environment, for this test setup you can go ahead and create an exception for this address.

2. Log in using the developer credentials created or obtained in the Setup OpenShift section above.

   You will see a list of projects, including the gateway project you created from the command line above.

   

   If you do not see your gateway project, you probably created it with a different user and will need to assign the policy role to to this user.

3. Click on the gateway link and you will see the Overview tab.

   OpenShift downloaded the code for APIcast and started the deployment. You may see the message Deployment #1 running when the deployment is in progress.

   When the build completes, the UI will refresh and show two instances of APIcast ( 2 pods ) that have been started by OpenShift, as defined in the template.

   

   Each APIcast instance, upon starting, downloads the required configuration from 3scale using the settings you provided on the Integration page of your 3scale Admin Portal.

   OpenShift will maintain two APIcast instances and monitor the health of both; any unhealthy APIcast instance will automatically be replaced with a new one.

4. To allow your APIcast instances to receive traffic, you need to create a route. Start by clicking on Create Route.

   

   Enter the same host you set in 3scale above in the section Public Base URL (without the http:// and without the port) , e.g. gateway.openshift.demo, then click the Create button.

   

   For every 3scale service you define, you must create a new route.

1. List all repositories: sudo yum repolist all.
2. Find the *-extras repository.
3. Enable the extras repository: sudo yum-config-manager --enable rhui-REGION-rhel-server-extras.
4. Install the Docker containerized environment package: sudo yum install docker.

1. Start the Docker daemon:

   sudo systemctl start docker.service.

2. Check if the Docker daemon is running:

   sudo systemctl status docker.service.

1. Run APIcast in a Docker-formatted container:

   sudo docker run --name apicast --rm -p 8080:8080 -e THREESCALE_PORTAL_ENDPOINT=https://<access_token>@<domain>-admin.3scale.net registry.redhat.io/3scale-amp2/apicast-gateway-rhel7:3scale2.8

   Here, <access_token> is the Access Token for the 3scale Account Management API. You can use the Provider Key instead of the access token. <domain>-admin.3scale.net is the URL of your 3scale admin portal.

Procedure

1. Download a ready to use Podman container image from the Red Hat registry:

   podman pull registry.redhat.io/3scale-amp2/apicast-rhel7:3scale2.8

2. Run APIcast in a Podman:

   podman run --name apicast --rm -p 8080:8080 -e THREESCALE_PORTAL_ENDPOINT=https://<access_token>@<domain>-admin.3scale.net registry.redhat.io/3scale-amp2/apicast-gateway-rhel7:3scale2.8

   Here, <access_token> is the Access Token for the 3scale Account Management API. You can use the Provider Key instead of the access token. <domain>-admin.3scale.net is the URL of your 3scale Admin Portal.

   This command runs a Podman container engine called apicast on port 8080 and fetches the JSON configuration file from your 3scale Admin Portal. For other configuration options, see Installing APIcast.