Optimizing your Hybrid Cloud Operating System Experience
summary
Describes a move from Ansible/RPM node-by-node upgrades to an operator-driven flow that builds and pushes per-cluster OS artifacts via an on-cluster image build, stores outputs in a registry, and boots worker nodes into layered OS images so configuration becomes the image source of truth. Claims include reduced config drift, transactional updates with atomic rollbacks, and hosted-management where a central cluster builds and serves images for many hosted clusters; gaps: SSH key handling, reboot-sensitive changes, kernel story.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:07Hybrid cloud OS problem
- 3:37OpenShift evolution 1→2
- 7:53CoreOS acquisition transition
- 11:25OS config limits
- 12:05Image-based OS config
- 17:47Image-based updates workflow
- 22:46Image-based update gaps
- 24:10Hosted centralized architecture
- 27:18Devs & admins benefits
- 28:00Q&A
related talks
45mIT Revolution: SLOs, DevOps, & Software-Defined Datacenter - Cloud Efficiency
33mEasily expand your on-premises OpenShift cluster
43mMoving the Unmovable: migrating from VMs to K8s
22mkOps: Recent Advances and the Journey to an OSS Kubernetes Distribution
31mThe Lightweight Cloud Servers War Begins
50mOps issues
21mHybrid Cloud - nothing to worry about! 🌥️
24mCoreOS Demystified – The Specialized OS Powering OpenShift and Containers