Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for non-Linux local test environments #151

Open
detiber opened this issue Mar 24, 2022 · 1 comment
Open

Support for non-Linux local test environments #151

detiber opened this issue Mar 24, 2022 · 1 comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@detiber
Copy link
Contributor

detiber commented Mar 24, 2022

Currently the only way to test locally with VMs is to use the Tinkerbell sandbox setup with Vagrant/libvirt on LInux.

The Tinkerbell sandbox also supports Vagrant/Virtualbox, which would provide a more cross-platform local test environment, but due to the networking configuration, does not work with streaming the sigs.k8s.io/image-builder based images from ghcr.io, and the resulting images would fail due to networking configuration even if they were written properly.

We need to either have a way for users to consume the published image-builder built images on Vagrant/Virtualbox or have another way(s) of running a local test environment using Windows and Mac.

Expected Behaviour

Mac/Windows users to have a way to run a local test environment using VMs

Current Behaviour

The only way to run a local test environment on VMs today is on Linux using Vagrant/Libvirt

Possible Solutions

  • Enable support for Tinkerbell sandbox Vagrant/Virtualbox environments either by updating hook and sigs.k8s.io/image-builder to support the Virtualbox networking configuration by default
  • Possibly support the Virtualbox networking environment using a combination of:
    • Configuring the Tinkerbell hardware networking configuration differently to better support the VirtualBox networking config
    • Ensuring that hook properly initializes all defined networking devices listed in the hardware configuration
    • Have a cluster template that can be used with Vagrant/Virtualbox to properly configure the networking devices defined in Hardware and not just the first device.
      • This may also require some changes to the cloud-init configuration injected into the written image by the CAPT-generated workflow template, longer term if this is needed it should be addressed via proper cloud-init support for Tinkerbell
  • Provide an alternative setup for local VMs on Windows/Mac (preferably adding support to tinkerbell/sandbox instead of a one-off setup for this repo).
@detiber detiber self-assigned this Mar 24, 2022
@mmlb mmlb added kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Apr 19, 2022
@chrisdoherty4 chrisdoherty4 added priority/backlog Higher priority than priority/awaiting-more-evidence. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Aug 24, 2022
@mloskot
Copy link

mloskot commented Dec 19, 2023

Please, consider Hyper-V as Windows native.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Development

No branches or pull requests

4 participants