Add example of integration with kubevirt

[jangel97]

Greetings,

In our team, we handle important Ansible roles to configure various aspects of RHEL systems, such as sshd, firewalld, grub, crypto-policies, and more. Although we have implemented automated testing with Molecule and Podman, there are instances where manual testing on our RHEL hosts becomes necessary before we proceed with deployment. I propose the integration of Molecule with Kubevirt as a potential solution to this issue. Such an integration would allow us to quickly and effectively test our Ansible roles on actual VMs, enhancing our testing procedures and providing more reliable results.

Some benefits of testing on VMs:

1. System-level realism: Ephemeral VMs provide a complete, isolated guest OS environment, much like your production environment. Containers share the host's kernel and are not fully isolated. This difference can occasionally lead to inconsistencies between testing and production environments. With VM-based testing, you can ensure the roles will work as expected on the actual operating system.

2. Broader Compatibility: Not all applications or configurations are container-friendly, especially when they interact with the system at a low level. VMs provide broader compatibility for testing as they offer a full-fledged OS environment.

3. Improved Debugging: Since VMs provide an entire guest operating system, it is often easier to debug issues related to system services, kernel modules, and other low-level components.

4. Greater Variety of Testing: VMs can run different kernel versions, different operating systems, or different system-level configurations. In contrast, containers are somewhat limited by the features and configurations of the host kernel.

In this pull request, I have utilized ephemeral VMs as a part of my example to showcase the benefits of this approach. By harnessing the capabilities of ephemeral VMs, we can test our Ansible roles in a highly realistic environment that closely mirrors our actual production environment, taking full advantage of the benefits outlined above.

This example serves as a practical guide to illustrate how a real-world application of Molecule and Kubevirt integration can enhance our current testing methods, enabling more realistic testing.

[audgirka]

@jangel97 The tests are missing for this PR

[jangel97]

@ajinkyau , this PR is adding an example to the Molecule documentation, showing users how to connect Molecule with Kubevirt using the default driver. It's not clear, though, how we can test this new addition. Are there any testing procedures already in place for the existing documentation, like the one we have for Podman integration https://ansible.readthedocs.io/projects/molecule/podman, that we can use as a reference?

[jangel97]

@ajinkyau , this PR is adding an example to the Molecule documentation, showing users how to connect Molecule with Kubevirt using the default driver. It's not clear, though, how we can test this new addition. Are there any testing procedures already in place for the existing documentation, like the one we have for Podman integration https://ansible.readthedocs.io/projects/molecule/podman, that I can use as a reference?

I've already conducted some tests in my environment, using a few different versions of Ansible. These tests were performed using an OpenShift cluster with Kubevirt available, and everything worked as expected for me using the code provided in the PR.

[zhan9san]

@jangel97

Thanks for your contribution.

Please refer to the changes in following files in #3978

tox.yml
mkdocs.yml
test_command.py