Reactive Endpoints with Quarkus on OpenShift
  • README
  • Setup the IBM Cloud Environment
    • Overview
    • Access the Cluster
    • Access IBM Cloud Shell
  • Setup the sample application
    • Exercise 1 - Deploy the example application via one script
    • YouTube - How to setup the sample application (optional)
  • Build a new version of the Microservice
    • Exercise 1 - Develop reactive Endpoints
    • Exercise 2 - Invoke Endpoints reactively
    • Exercise 3 - Deploy Service to OpenShift
    • Exercise 4 (optional) - Use distributed Logging
  • YouTube Videos related to the Exercises
    • Exercise 1 - Develop reactive Endpoints (optional)
    • Exercise 2 - Invoke Endpoints reactively (optional)
    • Exercise 3 - Deploy Service to OpenShift (optional)
    • Exercise 4 - Use distributed Logging (optional)
  • Additional Resources
    • Blog posts related to reactive
    • Workshop: Reactive Messaging with Quarkus on OpenShift
    • Cloud-Native-Starter project
    • Cloud-Native-Starter project reactive
  • Known Issues
    • Quarkus needs Apache Maven 3.6.2+
Powered by GitBook
On this page
  • Step 1: Set up Terminal
  • Step 2: Get the Code
  • Step 3. Get Access to OpenShift

Was this helpful?

  1. Setup the IBM Cloud Environment

Access IBM Cloud Shell

PreviousAccess the ClusterNextExercise 1 - Deploy the example application via one script

Last updated 4 years ago

Was this helpful?

For this workshop we'll be using the IBM Cloud Shell. The IBM Cloud Shell is a cloud-based shell workspace that you can access through your browser. It's preconfigured with the full IBM Cloud CLI and other 3rd party CLIs like OpenShift's oc, Helm's helm and Kubernetes' kubectl.

Step 1: Set up Terminal

When using OpenShift on IBM Cloud no client side setup is required for this workshop. Instead we will use the IBM Cloud Shell (Beta) which comes with all necessary CLIs (command line tools).

In your browser, login to the Dashboard. Make sure you select your own account in the account list at the top, then click on the IBM Cloud Shell icon.

Note: Your workspace includes 500 MB of temporary storage. This session will close after an hour of inactivity. If you don't have any active sessions for an hour or you reach the 30-hour weekly usage limit, your workspace data is removed.

This is what you should see:

When using OpenShift locally, you need a local terminal and the following tools:

  • Java 9 or higher

Step 2: Get the Code

In the IBM Cloud Shell execute the following command:

git clone https://github.com/IBM/cloud-native-starter.git
cd cloud-native-starter/reactive
ROOT_FOLDER=$(pwd)

Step 3. Get Access to OpenShift

The select 'OpenShift' in the burger menu in the upper left corner followed by 'Clusters'.

Click on your cluster.

Open the OpenShift web console.

From the dropdown menu in the upper right of the page, click 'Copy Login Command'.

Click on 'Display Token', then copy and paste the command 'Log in with this token' into your terminal in the IBM Cloud Shell.

Login to OpenShift in IBM Cloud Shell

oc login https://c1XX-XX-X.containers.cloud.ibm.com:XXXXX --token=xxxxxx'

![openshift-login3openshift-login3.png)

Open the . In the row at the top switch from your own account to the IBM account given to you by the instructor from the pulldown in the uper right corner.

git
curl
oc
mvn
IBM Cloud Dashboard
IBM Cloud
cloud-shell-launch
cloud-shell
cloud-shell-clone
openshift-console-launch1
openshift-console-launch2
Open the OpenShift web console
openshift-login1
openshift-login2