DO180 Red Hat OpenShift Administration I: Operating a Production Cluster — Lesson 2: Projects, Applications, Builds, Deployments, Services, and Routes

Learning Objectives

• Explain the structures, services, data, settings, roles, and dependencies governing projects and namespaces and application deployment.
• Implement and validate builds, services, and routes using reviewable evidence.
• Evaluate the condition where a change succeeds in one environment but fails elsewhere because inventory, policy, version, or runtime assumptions differ and select a proportionate corrective response.

Detailed Topics

• projects and namespaces applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• application deployment applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• builds applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• services applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• routes applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.

Instructor Demonstration

The instructor traces a platform operations team onboarding containerized services onto a shared OpenShift production cluster. The walkthrough connects navigation, commands, configuration logic, system messages, and evidence captured in the OpenShift workload operations portfolio, deployment evidence, health checks, and incident runbook. It also tests the exception where a change succeeds in one environment but fails elsewhere because inventory, policy, version, or runtime assumptions differ.

Hands-On Exercise

Complete a controlled Red Hat exercise covering Projects, Applications, Builds, Deployments, Services, and Routes and preserve the verified result in the OpenShift workload operations portfolio, deployment evidence, health checks, and incident runbook.

1. Confirm scope, prerequisites, versions, identities, dependencies, and acceptance criteria.
2. Execute the workflow while recording commands, settings, outputs, events, and system messages.
3. Test normal behavior, one boundary condition, and the stated exception.
4. Document corrections, evidence, ownership, retest criteria, rollback, and handover actions.

Scenario Analysis

• Identify which object, service, policy, setting, or sequence most strongly influences projects and namespaces.
• Compare two defensible responses and explain technical, security, operational, and support trade-offs.
• Determine how the OpenShift workload operations portfolio, deployment evidence, health checks, and incident runbook should be approved, retained, retested, and updated.

Troubleshooting Guidance

Start where expected behavior first differs from the observed result. Check prerequisites, identity, configuration order, version compatibility, connectivity, status, resource limits, and evidence separately. Treat “a change succeeds in one environment but fails elsewhere because inventory, policy, version, or runtime assumptions differ” as a hypothesis until commands, logs, settings, and retest outcomes confirm the cause.

Validation Checklist

• Required platform components, identities, permissions, settings, and dependencies are present.
• The OpenShift workload operations portfolio, deployment evidence, health checks, and incident runbook connects each conclusion to objective, reviewable evidence.
• Normal processing, a boundary condition, dependency behavior, and the stated exception were tested.
• Corrections, ownership, retest criteria, rollback, documentation, and operational handover are complete.

Lesson Outcome

Learners can apply Projects, Applications, Builds, Deployments, Services, and Routes, explain the resulting platform behavior, and defend the outcome through the OpenShift workload operations portfolio, deployment evidence, health checks, and incident runbook.