OpenShift for the Enterprise or What Could Possibly Go Wrong
summary
Ten concrete operational lessons for running OpenShift at scale: prefer many small nodes (30–40 containers) over single big nodes (community limit ~120) to avoid painful evacuations; use Prometheus and Grafana for capacity forecasting; automate provisioning with Ansible automation and provide a one‑click CI/CD pipeline; run at least two pods for production and exercise failure with chaos testing; scale backends too — a real case goes from 15k to 60k requests and leaves ~90 million pending; prefer managed DBs or mix local/dev containers; encrypt persistent volumes.
AI-written summary · about
chapters (5)
related talks
50mOpenShift in Production: 7 Pitfalls to Avoid
36mHow to run like a startup with enterprise Kubernetes
41mOpenShift: a Kubernetes Story in an Enterprise Environment
44mPerformance and Scalability Tuning Kubernetes for OpenShift and Docker
22mOpenShift, or Kubernetes on steroids
47m101 - Deploy with OpenShift in an Enterprise Context
21mOur Experiences with Red Hat OpenShift in the Corporate World
52mOperating OpenSearch at Scale: Lessons From Managing 10,000+ Clusters Across...