Building High Quality OpenShift Applications
summary
Concrete rules and tools for production quality: keep config out of image using ConfigMap/Secret so the same image promotes across envs, set CPU/memory requests and limits, use liveness/readiness probes and PodDisruptionBudgets, and ensure graceful termination; centralize logs to ELK or Splunk and monitor with Prometheus and dashboards; use service mesh, trusted base images, separate build vs runtime images, restricted SCC and TLS; favor one process per container, implement circuit breakers and retries, and follow testing targets like 70% unit tests, 20% integration, 5–10% manual.
AI-written summary · about
chapters (29)
- 0:00Introduction
- 0:39What is OpenShift
- 1:11Keep application config file outside of the image
- 2:24Resource request and limit
- 3:15Liveness and readiness
- 4:15Port disruption budget
- 5:01Ensure application part terminates gracefully
- 5:46Run only one process per container
- 6:34Implement application monitoring
- 7:12Implement application logs
- 8:29Trusted base image
- 9:27Build image vs onetime image
- 10:02Restricted security context constraint
- 10:34Always communicate using TLS
- 11:01Application Layer
- 11:38Single Responsibility
- 12:07Software Entity
- 12:28Substitution Principle
- 13:09Client Specific Interface
- 14:03Dependency inversion
- 15:09Selfcontainment principle
- 15:42Image immutability principle
- 16:10Observability principle
- 16:38Life cycle conformant principle
- 17:22Process disposability principle
- 18:08Onetime confinement principle
- 18:40Design patterns
- 19:08TDD
- 19:52Testing Pyramid
related talks
56m## Developer toolchain the cloud native way
31mDockerized app in production? YES WE CAN!!
43mPlatform Engineering 101: Building Developer Platforms
45mOpenShift the power of Kubernetes for developers
27mCrafting Seamless Development: Improving Kubernetes Operator Developer Experience
53mDesigning an Experience that Developers Love!
55mHow to develop apps on K8s and not die trying
31mGo From Dev to Prod