Red Hat OpenShift Developer II: Building Kubernetes Applications (DO288) — Lesson 4: CI/CD, Testing, Rollouts, Observability, Troubleshooting, and Delivery

Learning Objectives

• Explain the structures, services, data, settings, roles, and dependencies governing CI/CD concepts and automated testing.
• Implement and validate rollouts, logs and metrics, and troubleshooting using reviewable evidence.
• Evaluate the condition where a technically valid implementation creates operational risk because ownership, monitoring, rollback, or handover controls are incomplete and select a proportionate corrective response.

Detailed Topics

• CI/CD concepts applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• automated testing applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• rollouts applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• logs and metrics applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• troubleshooting applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.

Instructor Demonstration

The instructor traces an application team packaging and delivering a production-ready service through OpenShift-native development workflows. The walkthrough connects navigation, commands, configuration logic, system messages, and evidence captured in the containerized application repository, OpenShift manifests, test evidence, and delivery pipeline design. It also tests the exception where a technically valid implementation creates operational risk because ownership, monitoring, rollback, or handover controls are incomplete.

Hands-On Exercise

Complete a controlled Red Hat exercise covering CI/CD, Testing, Rollouts, Observability, Troubleshooting, and Delivery and preserve the verified result in the containerized application repository, OpenShift manifests, test evidence, and delivery pipeline design.

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 CI/CD concepts.
• Compare two defensible responses and explain technical, security, operational, and support trade-offs.
• Determine how the containerized application repository, OpenShift manifests, test evidence, and delivery pipeline design 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 technically valid implementation creates operational risk because ownership, monitoring, rollback, or handover controls are incomplete” 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 containerized application repository, OpenShift manifests, test evidence, and delivery pipeline design 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 CI/CD, Testing, Rollouts, Observability, Troubleshooting, and Delivery, explain the resulting platform behavior, and defend the outcome through the containerized application repository, OpenShift manifests, test evidence, and delivery pipeline design.