Building Secure & Reliable Edge Images Using RHEL for Edge Blueprinting & OSTree
summary
RHEL for Edge uses Image Builder, blueprints, podman/containerfiles, composer CLI and OSTree to produce immutable QCOW2/VMDK images; the demo builds a v1 image with httpd, signs the OSTree commit with GPG, pushes a v2 with ansible added, and performs a live boot switch to the new version showing httpd and ansible present. The workflow supports OSTree commit signed with GPG, atomic OS image updates, and scales to fleets (example: 5,000 devices) managed via Edge Manager.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:03Edge deployment challenges
- 2:27Traditional vs edge architectures
- 3:31Immutable vs mutable design
- 3:51Podman containers explained
- 5:17Atomic updates for devices
- 6:00Container registries management
- 7:05OSTree blueprints for images
- 8:11Security best practices
- 9:22Live demo setup
- 10:12Signing OSTree commits
- 14:56Composer CLI for images
- 18:57Deploying and testing images
- 19:41BootC atomic updates
- 24:54Switching image versions
- 28:21Red Hat Edge Manager
- 29:25When to use RHEL for Edge
- 30:50Q&A
related talks
28mBuilding an image pipeline using CentOS Stream and Image Builder
23mCreate your own custom Fedora IoT images
34mWhat's new in Image Builder?
27mApplying CI/CD Patterns to Image Mode for RHEL
34mDevice provisioning at the Edge
22mRe-igniting oVirt Node
32mResiliency at the Edge
34mApplication Configuration Management at the Edge: Taming Thousands of Deployment Targets