Files
k3s-ansible/molecule/default/molecule.yml
T
Timothy Stewart 68d03acc68 test(molecule): update Vagrant boxes to current releases
- Use published Bento boxes for Ubuntu 26.04, Debian 13, and Rocky Linux 10.1.\n- Pin exact VirtualBox amd64 box versions in CI.\n- Remove the obsolete Ubuntu SSH workaround and update fixtures.
2026-08-01 19:13:48 -05:00

106 lines
2.6 KiB
YAML

---
dependency:
name: galaxy
driver:
name: vagrant
# The Vagrant driver warns that parallel VirtualBox creation can cause
# platform issues. Keep this five-node, mixed-distribution scenario serial.
parallel: false
platforms:
- name: control1
box: bento/ubuntu-26.04
memory: 1024
cpus: 2
groups:
- k3s_cluster
- master
# Keep adapter 2 stable across linked-clone rebuilds so stale host-only
# neighbor state still identifies the current scenario guest.
provider_raw_config_args:
- "customize ['modifyvm', :id, '--mac-address2', '080027A13038']"
interfaces:
- network_name: private_network
ip: 192.168.30.38
- name: control2
box: bento/debian-13
memory: 1024
cpus: 2
groups:
- k3s_cluster
- master
provider_raw_config_args:
- "customize ['modifyvm', :id, '--mac-address2', '080027A13039']"
interfaces:
- network_name: private_network
ip: 192.168.30.39
- name: control3
box: bento/rockylinux-10.1
memory: 1024
cpus: 2
groups:
- k3s_cluster
- master
provider_raw_config_args:
- "customize ['modifyvm', :id, '--mac-address2', '080027A13040']"
interfaces:
- network_name: private_network
ip: 192.168.30.40
- name: node1
box: bento/ubuntu-26.04
memory: 1024
cpus: 2
groups:
- k3s_cluster
- node
provider_raw_config_args:
- "customize ['modifyvm', :id, '--mac-address2', '080027A13041']"
interfaces:
- network_name: private_network
ip: 192.168.30.41
- name: node2
box: bento/rockylinux-10.1
memory: 1024
cpus: 2
groups:
- k3s_cluster
- node
provider_raw_config_args:
- "customize ['modifyvm', :id, '--mac-address2', '080027A13042']"
interfaces:
- network_name: private_network
ip: 192.168.30.42
provisioner:
name: ansible
env:
ANSIBLE_VERBOSITY: 1
playbooks:
create: create.yml
converge: ../resources/converge.yml
side_effect: ../resources/reset.yml
verify: ../resources/verify.yml
inventory:
links:
group_vars: ../../inventory/sample/group_vars
scenario:
test_sequence:
- dependency
- cleanup
- destroy
- syntax
- create
- prepare
- converge
# idempotence is not possible with the playbook in its current form.
- verify
# We are repurposing side_effect here to test the reset playbook.
# This is why we do not run it before verify (which tests the cluster),
# but after the verify step.
- side_effect
- cleanup
- destroy