Red Hat OpenShift Installation Lab (DO322) — Lesson 2: Installer-Provisioned and User-Provisioned Installation Workflows

Learning Objectives

• Explain the structures, services, data, settings, roles, and dependencies governing installation program and install-config.
• Implement and validate IPI workflow, UPI workflow, and bootstrap process 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

• installation program applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• install-config applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• IPI workflow applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• UPI workflow applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• bootstrap process applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.

Instructor Demonstration

The instructor traces an infrastructure team building a repeatable OpenShift installation for a production-ready platform. The walkthrough connects navigation, commands, configuration logic, system messages, and evidence captured in the OpenShift installation plan, infrastructure readiness checklist, installation evidence, and recovery procedure. 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 Installer-Provisioned and User-Provisioned Installation Workflows and preserve the verified result in the OpenShift installation plan, infrastructure readiness checklist, installation evidence, and recovery procedure.

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 installation program.
• Compare two defensible responses and explain technical, security, operational, and support trade-offs.
• Determine how the OpenShift installation plan, infrastructure readiness checklist, installation evidence, and recovery procedure 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 installation plan, infrastructure readiness checklist, installation evidence, and recovery procedure 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 Installer-Provisioned and User-Provisioned Installation Workflows, explain the resulting platform behavior, and defend the outcome through the OpenShift installation plan, infrastructure readiness checklist, installation evidence, and recovery procedure.