This is a brief overview aimed at system administrators in getting accustomed to what OpenShift actually looks like installed on a host, and a common places to look when things go wrong. What should be running (systemctl) Nodes Masters Viewing Logs Storage Management What’s Next? What should be running (systemctl) At a high level, a host in an OpenShift cluster could include the following components:
After having gone through the process of building an OpenShift environment, it’s important to go through a few validation steps to ensure that all components are in proper working order. This document walks you through those steps. Validate Nodes Validate Status of Default Project Check that Registry Is Running Check that Router is Running Run Diagnostics Create an Application But wait, something didn’t work! Other Resources Validate Nodes # oc get nodes Check the output to ensure that:
OpenShift Monitoring is an ever evolving problem space, with many layers, approaches, and complexities. We attempt to unpack them here. Overview Ensuring a cluster is healthy Docker Nodes & Masters API Endpoints Ensuring a cluster has adequate capacity What’s Next? Overview Note Before reading this guide, we recommend first reading An Overview of OpenShift for System Admins. The following document intends to provide starting guidance on how to build a monitoring approach for OpenShift.