Deploying in ephemeral environment

Before deploying ros-ocp-backend to ephemeral environment make sure you check Getting Started with Ephemeral Environments (EE) document to get access to the ephemeral openshift cluster and also go through Installing and using bonfire document.

Once you have installed bonfire cli tool and fetched the openshift login token using Installing and using bonfire document you can follow along with this document.

Usage

Note - Until ros-ocp-backend is onboarded to app-interface copy paste the custom bornfire configuration in ~/.config/bonfire/config.yaml from the below section custom bonfire config

Use the below bonfire command to deploy ros-ocp-backend in EE.

# bonfire deploy ros-ocp-backend

Running the above command will reserve namespace for you in the EE cluster and will deploy the ros-ocp-backend and dependent service(ingress, kafka, kruize, etc) in the reserved namespace.

At the end of above command execution it will print the name of reserved namespace, this namespace is by default reserved for an hour but reservation can be extend using below command.

# bonfire namespace extend -d 2h <namespace name>

• -d flag is for the duration.

View all the deployed services

# oc get pods -n <namespace name>

Custom bonfire config

If you want to use the custom images or custom parameters or want to use the locally create/modified clowdapp.yaml file while deploying ros-ocp-backend then you need to modify ~/.config/bonfire/config.yaml file as below

# Bonfire deployment configuration
apps:
- name: ros-ocp-backend
  components:
    - name: ros-ocp-backend-test
      host: local
      repo: ~/redhat-projects/ros-ocp-backend/
      path: /clowdapp.yaml
      parameters:
        IMAGE_TAG: test
        IMAGE: quay.io/supatil/ros-ocp-backend
        KRUIZE_IMAGE: quay.io/supatil/autotune_operator
        KRUIZE_IMAGE_TAG: test2