Container Service

Access to on-campus resources Services hosted on-campus will need to allow access for Container Service applications. Firewall rules for on-campus systems that your application depends upon will need to be opened to compute nodes within the OpenShift cluster. The full subnet range will need to be specified, as nodes could have any IP in the range. In the production cluster your application could have any IP within this range:
Overview OpenShift Auto-scaling Documentation. OpenShift Requesting CPU Resources Documentation. Auto-Scaling
Overview As outlined on the Container Service website, updating applications and application images is a customer responsibility. This starts with selecting an appropriate base image, regularly checking for image updates, rebuilding your application to utilize updated images, and regularly moving your base image forward to keep it current. Although no one suggestion will address all situations, some guidelines apply to most.
Overview OpenShift Documentation: Copying Files to or from a Container Copying and Syncing Files The oc cp and oc rsync commands work similar to their bash equivalents. Using them, it is possible to access / update files in a pod from the command line. E.g. The command oc cp howdy-1-1234:/var/log/messages .  will copy log files from the howdy-1-1234 pod to the current directory on your local machine.
Overview OpenShift documentation on publishing routes can be found here. Users of the production cluster,, can self-publish routes that end in: No DNS changes are required for URLs within
Viewing Metrics For A Project Users can view pod-level metrics on the Project Overview page, and on the Pods page at Applications > Pods > choose pod name. Select Metrics from tabbed list.
Overview OpenShift Deployments Documentation Rolling Back Teams may wish to roll back to a previous version of a deployed application in cases where the current version has incorrectable errors. Instructions for how to do that are here. The key command is:
Overview For developers creating web applications and services, OpenShift provides an easy means to route traffic to your application, the route.
OpenShift documentation on routes is here. All routes should be encrypted via SSL certificates. Routes within the domain can utilize a wildcard certificate provided for the Container Service. Simply specify 'edge termination' and do not include any certificates.
Overview OpenShift CLI reference for viewing logs. The Container Service retains log data for 90 days. OpenShift UI Logs for running pods are visible from within the OpenShift UI.  Go to: Applications > Pods, and select Logs from the following tabbed list: