Terminal access

http://workshop-terminal-terminal-YOUR#.apps.example.redhatgov.io

Choose a running pod and shell into it:

$ oc get pods
$ oc exec PODNAME -it /bin/bash

You are now executing a bash shell running in the container of the pod. Let’s kill our webapp and see what happens.

If we had multiple containers in the pod we could use "-c CONTAINER_NAME" to select the right one

Choose a running pod and shell into its container:

$ pkill -9 node

This will kick you out off the container with an error like “Error executing command in container”

Do it again - shell in and execute the same command to kill node

Watch for the container restart

$ oc get pods -w

If a container dies multiple times quickly, OpenShift is going to put the pod in a CrashBackOff state. This ensures the system doesn’t waste resources trying to restart containers that are continuously crashing.

Web Console access

https://console-openshift-console.apps.example.redhatgov.io

Navigate to browse the pods list, and click on a running pod

In the tab bar for this pod, click on "Terminal"

Click inside the terminal view and type $ pkill -9 node

This is going to kill the node.js web server, and kick you off of the container’s terminal.

Click the refresh button (on your web browser), and do that a couple more times

Go back to the pod overview

If the container dies multiple times so quickly; then OpenShift is going to put the pod in a CrashBackOff state. This ensures the system doesn’t waste resources trying to restart containers that are continuously crashing.