NOTE: This step is only applicable if you are deploying a backend service to the ConsoleDot OSD cluster. 

Purpose (the why):

• If you are deploying a backend service to the ConsoleDot OSD cluster, your service backend is deployed via[ ConsoleDot operator "Clowder"|https://github.com/RedHatInsights/clowder]. 

Responsible: 

• App Team Developers, App Team Engineering Manager

Prerequisite/dependencies:

• Understanding of the infrastructure requirements (eg. Kafka, database, etc.)
• App-interface access for teams to deploy using bonfire. 

Next task: 

• CI/CD Delivery

Deliverable/completion criteria: 

• App backend service is deployed to an ephemeral environment using Clowder operator.

Expected duration/effort:

• ~1 hour to 2 days (depends on whether the app was initially created with Clowder in mind).  

Due date: 

• First deployment to pre-production environment.

Supporting documentation/best practices: 

• How to start using Clowder
• Pre-staging deployment via Clowder & ephemeral environments
• Benefits of Clowder & Readme
• Using proxy for stage environment access

Exception process:

• N/A

How to get help:

• Talk to the DevProd team in the CoreOS slack channel #team-consoledot-devprod.