DO370 – Enterprise Kubernetes Storage with Red Hat OpenShift Data Foundation — Lesson 1: ODF Architecture, Kubernetes Storage APIs, Deployment Modes, and Installation

Learning Objectives

• Explain the architecture, purpose, dependencies, and expected behavior of ODF architecture, Kubernetes storage APIs, and internal mode.
• Apply external mode and installation while preserving reviewable technical evidence.
• Recognize and correct the condition where an unstated prerequisite or ownership gap causes the initial design to be incomplete.

Detailed Topics

• ODF architecture: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• Kubernetes storage APIs: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• internal mode: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• external mode: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• installation: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.

Instructor Demonstration

The instructor demonstrates odf architecture, kubernetes storage apis, deployment modes, and installation by tracing architecture, commands, configuration, system messages, and evidence. The walkthrough tests how an unstated prerequisite or ownership gap causes the initial design to be incomplete and explains how to isolate the cause without masking related issues.

Hands-On Exercise

Establish a controlled baseline for ODF Architecture, Kubernetes Storage APIs, Deployment Modes, and Installation and add the verified result to the ODF deployment design, storage-class catalog, workload tests, monitoring evidence, and recovery procedure.

1. Confirm scope, versions, access, dependencies, assumptions, and acceptance criteria.
2. Perform the workflow while recording commands, configuration, output, events, and decisions.
3. Test the normal path and one course-specific exception or boundary condition.
4. Retest the correction and document rollback, ownership, and follow-up actions.

Scenario Analysis

• Identify which dependency most strongly influences ODF architecture in the stated scenario.
• Compare two approaches for external mode and explain the security, reliability, performance, and support trade-offs.
• Decide what evidence must be retained in the ODF deployment design, storage-class catalog, workload tests, monitoring evidence, and recovery procedure before operational acceptance.

Troubleshooting Guidance

Begin with the first observable difference from the expected result. Check architecture, scope, identities, prerequisites, and starting conditions separately, then correlate logs, events, commands, metrics, and configuration history. Treat the assumption that an unstated prerequisite or ownership gap causes the initial design to be incomplete as a hypothesis until a reproducible retest confirms the cause.

Validation Checklist

• The required architecture, scope, identities, prerequisites, and starting conditions were checked and recorded.
• The normal path and a course-specific exception were tested.
• The ODF deployment design, storage-class catalog, workload tests, monitoring evidence, and recovery procedure links conclusions to commands, configuration, logs, metrics, or other objective evidence.
• Corrective actions, rollback, ownership, and handover notes are complete.

Lesson Outcome

Learners can apply ODF Architecture, Kubernetes Storage APIs, Deployment Modes, and Installation, explain the observed platform behavior, and support the result with a reviewable ODF deployment design, storage-class catalog, workload tests, monitoring evidence, and recovery procedure.