TL112 – Red Hat Transformational Learning: Introduction to Pragmatic Site Reliability Engineering — Lesson 1: SRE Principles, Service Ownership, Reliability Risk, and Customer Expectations

Learning Objectives

• Explain the architecture, purpose, dependencies, and expected behavior of SRE principles, service ownership, and customer journeys.
• Apply reliability risks and operating responsibilities 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

• SRE principles: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• service ownership: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• customer journeys: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• reliability risks: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• operating responsibilities: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.

Instructor Demonstration

The instructor demonstrates sre principles, service ownership, reliability risk, and customer expectations 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 SRE Principles, Service Ownership, Reliability Risk, and Customer Expectations and add the verified result to the service reliability charter, SLI and SLO register, error-budget policy, and improvement roadmap.

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 SRE principles in the stated scenario.
• Compare two approaches for reliability risks and explain the security, reliability, performance, and support trade-offs.
• Decide what evidence must be retained in the service reliability charter, SLI and SLO register, error-budget policy, and improvement roadmap 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 service reliability charter, SLI and SLO register, error-budget policy, and improvement roadmap 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 SRE Principles, Service Ownership, Reliability Risk, and Customer Expectations, explain the observed platform behavior, and support the result with a reviewable service reliability charter, SLI and SLO register, error-budget policy, and improvement roadmap.