Containers, Kubernetes, and Red Hat OpenShift Administration II (DO285) – 4.6 — Lesson 2: Kubernetes and OpenShift Workloads, Projects, Services, Routes, and Configuration

Learning Objectives

• Explain the structures, services, data, settings, roles, and dependencies governing Kubernetes objects and projects.
• Implement and validate deployments, services and routes, and configuration and secrets 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

• Kubernetes objects applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• projects applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• deployments applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• services and routes applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• configuration and secrets applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.

Instructor Demonstration

The instructor traces an administrator progressing from container operations to production OpenShift cluster configuration in one integrated learning path. The walkthrough connects navigation, commands, configuration logic, system messages, and evidence captured in the integrated container and OpenShift administration portfolio, cluster baseline, and troubleshooting runbook. 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 Kubernetes and OpenShift Workloads, Projects, Services, Routes, and Configuration and preserve the verified result in the integrated container and OpenShift administration portfolio, cluster baseline, and troubleshooting runbook.

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 Kubernetes objects.
• Compare two defensible responses and explain technical, security, operational, and support trade-offs.
• Determine how the integrated container and OpenShift administration portfolio, cluster baseline, and troubleshooting runbook 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 integrated container and OpenShift administration portfolio, cluster baseline, and troubleshooting runbook 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 Kubernetes and OpenShift Workloads, Projects, Services, Routes, and Configuration, explain the resulting platform behavior, and defend the outcome through the integrated container and OpenShift administration portfolio, cluster baseline, and troubleshooting runbook.