kdevops sync up
summary
vagrant is unmaintained, so kdevops moves toward alternatives: ktest/Kconfig, Terraform/OpenTF, or running guests inside Kubernetes using virt (KVM-in-pods). A Kubernetes proof‑of‑concept runs FS‑tests (xfs, XFS profiles extended) successfully but hits SSH port‑forward fragility, pod scheduling and resume limitations. Clouds get automated Kconfig generation from AMI queries and per‑hyperscaler device overrides; EBS now exposes four drives by default. Kubernetes KVM inside pods works and PCI passthrough via dynamic Kconfig is implemented though PCI reset permissions still need a kernel fix.
AI-written summary · about
chapters (8)
- 0:00Introduction and updates
- 2:06Vagrant replacement options
- 7:48Kubernetes bring-up method
- 18:25PCI passthrough and SSH setup
- 23:06Cross-platform support and licensing
- 28:09File system testing strategies
- 31:41Development and review process
- 33:27Self-hosting kdevops
related talks
22mkOps: Recent Advances and the Journey to an OSS Kubernetes Distribution
21mMy cluster is running… but does it actually work
35mYocto Continuous Integration in a Kube
35mAnd then there was k8s
35mKubernetes journey
43mMoving the Unmovable: migrating from VMs to K8s
32mAutomating and Testing Production Ready Kubernetes Clusters in the Public Cloud
32mKubernetes: Pimp My Laptop