How ashishagarwal143/openshift-march-2025 works
Project type and purpose
• This repository is a set of end-to-end hands-on labs for learning Red Hat OpenShift. Each “DayX” folder contains independent Kubernetes/OpenShift exercises: from simple static sites (Day2), to manifests for WordPress+MariaDB (Day7), Ingress (Day8), and a Java “Hello” microservice with Dockerfile, Deployment, Service and Route (Day9/Day10).
File structure
• Top-level folders Day1…Day10 each contain a README and one or more demos.
• “hello” subfolders in Day9 and Day10 hold a Java app (src/main/java/org/tektutor…), a Dockerfile and OpenShift YAML (Deployment, Service, Route).
• Day7/declarative-manifest-scripts demonstrates persistent volumes (PV), PVC, ConfigMaps, Secrets, Services and Deployments for MariaDB and WordPress.
• Day8/ingress shows an Ingress resource plus backend and ingress-controller Deployments/Services.
• Day2/lb is a static HTML demo behind an NGINX Deployment/Service.
Extract additional insights from the README
• The course is about installing and using OpenShift Local.
• No single monolithic app—each day is a standalone scenario illustrating a key Kubernetes/OpenShift concept.
a. Main components
• Developer workstation (source code, YAML manifests)
• Build system (local Docker-or-S2I build → container registry)
• OpenShift cluster
– Control plane (API Server, etcd, Controller Manager)
– Worker nodes (Kubelet, CRI-O)
• Workloads (per-day demos):
– Static site (NGINX Deployment + Service)
– Java Hello microservice (Deployment, Service, Route)
– Ingress controller + Ingress + Hello backend
– WordPress + MariaDB (Deployments, Services, PV/PVC, ConfigMap, Secret)
• External users & HTTP clients
b. Relationships and interactions
– Developer pushes code/manifests → local build → container image → image registry
– OpenShift pulls image → schedules Pods on nodes
– Services provide in-cluster discovery; Routes/Ingress expose HTTP(S) externally
– PV/PVC attach storage to database pods; ConfigMaps and Secrets inject configuration
c. Architectural patterns and design principles
– Immutable container images built from source (Dockerfile/S2I)
– Declarative YAML manifests for all resources (Infrastructure as Code)
– Logical separation: control plane vs. worker plane; frontend vs. backend vs. data store
– Use of Kubernetes primitives (Deployment, Service, Ingress, PV/PVC, ConfigMap, Secret)
d. Key technologies/frameworks
– OpenShift Local / OKD
– Kubernetes API objects (Deployment, Service, Route/Ingress, PVC, Secret, ConfigMap)
– Docker/S2I builds, container registry
– Java Spring-boot (HelloController), NGINX, MariaDB, WordPress