NOTE: This step is only applicable if you are running a service on the Hybrid Cloud Console OSD Cluster. 

Purpose (the why):

• In order to have your service available on console.redhat.com, you’ll need to have a service definition in 3scale, for our API gateway to proxy to.

Responsible:

• App Team Developers, App Team Engineering Manager

Prerequisite/dependencies: 

1. Service should be running in the same OpenShift Dedicated cluster as the HCC Platform.
2. Service should be accessible via the cluster's internal host/port via a service.

Next task: 

• N/A

Deliverable/completion criteria: 

• You have followed the[ 3Scale Onboarding guide|https://consoledot.pages.redhat.com/docs/dev/getting-started/gateway/index.html] and the steps outlined in the guide are complete.
• You have confirmed you can access your service via console.redhat.com/api/* directly.

Expected duration/effort:

• Onboarding can be completed same-day, but generally, we would ask for a sprint so that we can schedule the changes into our existing workload. 

Due date: 

• First deployment to a pre-production environment.

Supporting documentation/best practices: 

• Getting Started - Gateway Onboarding (VPN required) 

Exception process:

• N/A

How to get help:

• Contact kwalsh@redhat.com or rhn-support-cmitchel (engineering)