Skip to content

Latest commit

 

History

History
71 lines (50 loc) · 2.31 KB

openshift.md

File metadata and controls

71 lines (50 loc) · 2.31 KB
Raw

Example Setup with OpenShift

NOTE: This Guide was tested with OpenShift 3.11, if this doesn't work with newer OpenShift versions please open up an issue. Thank you! 👏

Prerequisites

This example expects you to have the following prerequisites.

  1. A running OpenShift Cluster
  2. oc, OpenShift CLI
  3. helm, helm3 recommended, to avoid tiller headache

Step 1. Log into the OpenShift cluster

# Log in with your OpenShift CLI
# You can copy the login command including your token from the web ui
oc login https://console.openshift.example.com --token=****

# Create a new project to hold the multi-juicer resources
oc new-project multi-juicer

Step 2. Installing MultiJuicer via helm

helm install multi-juicer oci://ghcr.io/juice-shop/multi-juicer/helm/multi-juicer

Step 3. Verify the app is running correctly

This step is optional, but helpful to catch errors quicker.

# lets test out if the app is working correctly before proceeding
# for that we can port forward the JuiceBalancer service to your local machine
oc port-forward service/juice-balancer 3000:3000

# Open up your browser for localhost:3000
# You should be able to see the MultiJuicer Balancer UI

# Try to create a team and see if everything works correctly
# You should be able to access a JuiceShop instances after a few seconds after creating a team,
# and after clicking the "Start Hacking" Button

# You can also try out if the admin UI works correctly
# Go back to localhost:3000/balancer
# To log in as the admin log in as the team "admin"
# The password for the team gets auto generated if not specified, you can extract it from the kubernetes secret:
oc get secrets juice-balancer-secret -o=jsonpath='{.data.adminPassword}' | base64 --decode

Step 4. Add a route to expose the app to the world

OpenShift lets you create routes to expose your app to the internet.

# Create the route.
# Make sure to adjust the hostname to match the one of your org.
# You can also perform this step easily via the OpenShift web ui.
oc create route edge juice-balancer --service juice-balancer --hostname multi-juicer.cloudapps.example.com

Step 4. Deinstallation

helm delete multi-juicer

# Delete the route
oc delete route edge juice-balancer