This issue is to open a discussion regarding the potential integration of krunkit as an alternative or replacement for vfkit in this repository. The goal is to explore the pros, cons, and implications of supporting krunkit, including compatibility, migration challenges, and any required changes to current workflows.
Areas to discuss:
- Feature parity between krunkit and vfkit
- Migration strategies or coexistence plans
- Impact on existing users and configurations
- Required updates to documentation and automation