Red Hat OpenShift Administration II: Configuring a Production Cluster (DO280) — Lesson 2: Networking, Ingress, Routes, Network Policies, and Persistent Storage

Learning Objectives

• Explain the structures, services, data, settings, roles, and dependencies governing cluster networking and ingress controllers.
• Implement and validate route options, network policies, and storage classes and claims 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

• cluster networking applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• ingress controllers applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• route options applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• network policies applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• storage classes and claims applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.

Instructor Demonstration

The instructor traces a cluster administration team preparing an OpenShift platform for secure, multi-team production use. The walkthrough connects navigation, commands, configuration logic, system messages, and evidence captured in the production cluster configuration baseline, access model, operations checklist, and resilience validation pack. 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 Networking, Ingress, Routes, Network Policies, and Persistent Storage and preserve the verified result in the production cluster configuration baseline, access model, operations checklist, and resilience validation pack.

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 cluster networking.
• Compare two defensible responses and explain technical, security, operational, and support trade-offs.
• Determine how the production cluster configuration baseline, access model, operations checklist, and resilience validation pack 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 production cluster configuration baseline, access model, operations checklist, and resilience validation pack 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 Networking, Ingress, Routes, Network Policies, and Persistent Storage, explain the resulting platform behavior, and defend the outcome through the production cluster configuration baseline, access model, operations checklist, and resilience validation pack.