Summary

  • An RHOCP cluster can be managed from the web console or by using the kubectl or oc command-line interfaces (CLI).

  • Use the --help option on any command to view detailed information about the command.

  • Projects provide isolation between your application resources.

  • Token authentication is the only guaranteed method to work with any RHOCP cluster, because enterprise SSO might replace the login form of the web console.

  • All administrative tasks require creating, viewing, and changing the API resources.

  • Kubernetes provides YAML- and JSON-formatted output options, which are ideal for parsing or scripting.

  • Operators provide the means of monitoring applications, performing health checks, managing over-the-air (OTA) updates, and ensuring that applications remain in your specified state.

  • The RHOCP web console incorporates useful graphs to visualize cluster and resource analytics.

  • The RHOCP web console provides an interface for executing Prometheus queries, visualizing metrics, and configuring alerts.

  • The monitoring stack is based on the Prometheus project, and it is configured to monitor the core RHOCP cluster components, by default.

  • RHOCP provides the ability to view logs in running containers and pods to ease troubleshooting.

  • You can collect resource definitions and service logs from your cluster by using the oc adm must-gather command.

Revision: do180-4.14-unknown