kubernetes-sigs
/
kubespray
mirror of https://github.com/kubernetes-sigs/kubespray.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
kubespray/roles/container-engine/cri-o/molecule/default/molecule.yml

58 lines
1.0 KiB
YAML
Raw Normal View History

Add CRI-O CI (#5460)
2020-04-22 21:09:52 +08:00
---
project: upgrade test dependencies and drop ansible-core 2.11 (#10034) Molecule 5.0 require ansible-core 2.12.10. So this commit we update ansible-core from 2.12.5 to 2.12.10. We also drop supporting two ansible-core version. Also we now use the "oldest" still supported ansible-core version as both 2.11 is EOL and not supported by molecule. tests/molecule: remove linting in molecule to support molecule 5 tests/molecule: remove role name check for molecule 5 support Kubespray doesn't use ansible galaxy style naming so we have to disable that check. contrib/inventory_builder: fix tox.ini for tox4 tests/molecule: fix get_playbook in testinfra tests tests: upgrade most tests requirements Exclude ansible-lint for now, I will do that in a separate PR. tests/molecule: force kvm driver option If we don't do this it fallbacks to qemu emulated on our CI for some reasons. Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@proton.ch>
2023-06-03 11:40:40 +08:00
role_name_check: 1
Add CRI-O CI (#5460)
2020-04-22 21:09:52 +08:00
driver:
name: vagrant
provider:
name: libvirt
platforms:
use cri-o from upstream instead of kubic/OBS (#9374) * [cri-o] use cri-o from upstream instead of kubic/OBS * [cri-o] add proper molecule coverage * [skopeo] download skopeo from upstream build * [cri-o] clean up legacy deployments * disable cri-o per-distribution variables
2022-10-19 20:47:05 +08:00
- name: ubuntu20
[cri-o] molecule switch from ubuntu 18 to ubuntu 20
2022-05-04 03:56:33 +08:00
box: generic/ubuntu2004
Enable crio 1.18 (#6197)
2020-05-28 15:42:15 +08:00
cpus: 2
memory: 1024
groups:
Replace kube-master with kube_control_plane (#7256) This replaces kube-master with kube_control_plane because of [1]: The Kubernetes project is moving away from wording that is considered offensive. A new working group WG Naming was created to track this work, and the word "master" was declared as offensive. A proposal was formalized for replacing the word "master" with "control plane". This means it should be removed from source code, documentation, and user-facing configuration from Kubernetes and its sub-projects. NOTE: The reason why this changes it to kube_control_plane not kube-control-plane is for valid group names on ansible. [1]: https://github.com/kubernetes/enhancements/blob/master/keps/sig-cluster-lifecycle/kubeadm/2067-rename-master-label-taint/README.md#motivation
2021-03-24 08:26:05 +08:00
- kube_control_plane
use cri-o from upstream instead of kubic/OBS (#9374) * [cri-o] use cri-o from upstream instead of kubic/OBS * [cri-o] add proper molecule coverage * [skopeo] download skopeo from upstream build * [cri-o] clean up legacy deployments * disable cri-o per-distribution variables
2022-10-19 20:47:05 +08:00
- kube_node
- k8s_cluster
project: upgrade test dependencies and drop ansible-core 2.11 (#10034) Molecule 5.0 require ansible-core 2.12.10. So this commit we update ansible-core from 2.12.5 to 2.12.10. We also drop supporting two ansible-core version. Also we now use the "oldest" still supported ansible-core version as both 2.11 is EOL and not supported by molecule. tests/molecule: remove linting in molecule to support molecule 5 tests/molecule: remove role name check for molecule 5 support Kubespray doesn't use ansible galaxy style naming so we have to disable that check. contrib/inventory_builder: fix tox.ini for tox4 tests/molecule: fix get_playbook in testinfra tests tests: upgrade most tests requirements Exclude ansible-lint for now, I will do that in a separate PR. tests/molecule: force kvm driver option If we don't do this it fallbacks to qemu emulated on our CI for some reasons. Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@proton.ch>
2023-06-03 11:40:40 +08:00
provider_options:
driver: kvm
CI: Replace CentOS 8 with AlmaLinux 8 before CentOS 8 EOL end of 2021 (#8297)
2022-01-05 18:20:33 +08:00
- name: almalinux8
box: almalinux/8
Centos, debian and fedora CRI-O repo (#6008) * replace removed repo with kubic repository for centos 7 * add crio configuration for centos8 * add crio configurations for debian * use correct crio version for fedora * simplify calulation of required crio version - gives possibility to overwrite * change default path for runc * change default for seccomp path * change default for conmon
2020-04-24 16:18:07 +08:00
cpus: 2
memory: 1024
groups:
Replace kube-master with kube_control_plane (#7256) This replaces kube-master with kube_control_plane because of [1]: The Kubernetes project is moving away from wording that is considered offensive. A new working group WG Naming was created to track this work, and the word "master" was declared as offensive. A proposal was formalized for replacing the word "master" with "control plane". This means it should be removed from source code, documentation, and user-facing configuration from Kubernetes and its sub-projects. NOTE: The reason why this changes it to kube_control_plane not kube-control-plane is for valid group names on ansible. [1]: https://github.com/kubernetes/enhancements/blob/master/keps/sig-cluster-lifecycle/kubeadm/2067-rename-master-label-taint/README.md#motivation
2021-03-24 08:26:05 +08:00
- kube_control_plane
use cri-o from upstream instead of kubic/OBS (#9374) * [cri-o] use cri-o from upstream instead of kubic/OBS * [cri-o] add proper molecule coverage * [skopeo] download skopeo from upstream build * [cri-o] clean up legacy deployments * disable cri-o per-distribution variables
2022-10-19 20:47:05 +08:00
- kube_node
- k8s_cluster
project: upgrade test dependencies and drop ansible-core 2.11 (#10034) Molecule 5.0 require ansible-core 2.12.10. So this commit we update ansible-core from 2.12.5 to 2.12.10. We also drop supporting two ansible-core version. Also we now use the "oldest" still supported ansible-core version as both 2.11 is EOL and not supported by molecule. tests/molecule: remove linting in molecule to support molecule 5 tests/molecule: remove role name check for molecule 5 support Kubespray doesn't use ansible galaxy style naming so we have to disable that check. contrib/inventory_builder: fix tox.ini for tox4 tests/molecule: fix get_playbook in testinfra tests tests: upgrade most tests requirements Exclude ansible-lint for now, I will do that in a separate PR. tests/molecule: force kvm driver option If we don't do this it fallbacks to qemu emulated on our CI for some reasons. Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@proton.ch>
2023-06-03 11:40:40 +08:00
provider_options:
driver: kvm
Fix crio runc path on Ubuntu (#6035)
2020-04-28 20:28:06 +08:00
- name: fedora
Use supported version of fedora in CI (#10108) * tests: replace fedora35 with fedora37 Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@proton.ch> * tests: replace fedora36 with fedora38 Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@proton.ch> * docs: update fedora version in docs Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@proton.ch> * molecule: upgrade fedora version Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@proton.ch> * tests: upgrade fedora images for vagrant and kubevirt Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@proton.ch> * vagrant: workaround to fix private network ip address in fedora Fedora stop supporting syconfig network script so we added a workaround here https://github.com/hashicorp/vagrant/issues/12762#issuecomment-1535957837 to fix it. * netowrkmanager: do not configure dns if using systemd-resolved We should not configure dns if we point to systemd-resolved. Systemd-resolved is using NetworkManager to infer the upstream DNS server so if we set NetworkManager to 127.0.0.53 it will prevent systemd-resolved to get the correct network DNS server. Thus if we are in this case we just don't set this setting. Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@proton.ch> * image-builder: update centos7 image Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@proton.ch> * gitlab-ci: mark fedora packet jobs as allow failure Fedora networking is still broken on Packet, let's mark it as allow failure for now. Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@proton.ch> --------- Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@proton.ch>
2023-08-08 15:50:12 +08:00
box: fedora/38-cloud-base
Centos, debian and fedora CRI-O repo (#6008) * replace removed repo with kubic repository for centos 7 * add crio configuration for centos8 * add crio configurations for debian * use correct crio version for fedora * simplify calulation of required crio version - gives possibility to overwrite * change default path for runc * change default for seccomp path * change default for conmon
2020-04-24 16:18:07 +08:00
cpus: 2
fix-ci-issue (#9640)
2023-01-05 16:11:58 +08:00
memory: 2048
Centos, debian and fedora CRI-O repo (#6008) * replace removed repo with kubic repository for centos 7 * add crio configuration for centos8 * add crio configurations for debian * use correct crio version for fedora * simplify calulation of required crio version - gives possibility to overwrite * change default path for runc * change default for seccomp path * change default for conmon
2020-04-24 16:18:07 +08:00
groups:
Replace kube-master with kube_control_plane (#7256) This replaces kube-master with kube_control_plane because of [1]: The Kubernetes project is moving away from wording that is considered offensive. A new working group WG Naming was created to track this work, and the word "master" was declared as offensive. A proposal was formalized for replacing the word "master" with "control plane". This means it should be removed from source code, documentation, and user-facing configuration from Kubernetes and its sub-projects. NOTE: The reason why this changes it to kube_control_plane not kube-control-plane is for valid group names on ansible. [1]: https://github.com/kubernetes/enhancements/blob/master/keps/sig-cluster-lifecycle/kubeadm/2067-rename-master-label-taint/README.md#motivation
2021-03-24 08:26:05 +08:00
- kube_control_plane
use cri-o from upstream instead of kubic/OBS (#9374) * [cri-o] use cri-o from upstream instead of kubic/OBS * [cri-o] add proper molecule coverage * [skopeo] download skopeo from upstream build * [cri-o] clean up legacy deployments * disable cri-o per-distribution variables
2022-10-19 20:47:05 +08:00
- kube_node
- k8s_cluster
project: upgrade test dependencies and drop ansible-core 2.11 (#10034) Molecule 5.0 require ansible-core 2.12.10. So this commit we update ansible-core from 2.12.5 to 2.12.10. We also drop supporting two ansible-core version. Also we now use the "oldest" still supported ansible-core version as both 2.11 is EOL and not supported by molecule. tests/molecule: remove linting in molecule to support molecule 5 tests/molecule: remove role name check for molecule 5 support Kubespray doesn't use ansible galaxy style naming so we have to disable that check. contrib/inventory_builder: fix tox.ini for tox4 tests/molecule: fix get_playbook in testinfra tests tests: upgrade most tests requirements Exclude ansible-lint for now, I will do that in a separate PR. tests/molecule: force kvm driver option If we don't do this it fallbacks to qemu emulated on our CI for some reasons. Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@proton.ch>
2023-06-03 11:40:40 +08:00
provider_options:
driver: kvm
use cri-o from upstream instead of kubic/OBS (#9374) * [cri-o] use cri-o from upstream instead of kubic/OBS * [cri-o] add proper molecule coverage * [skopeo] download skopeo from upstream build * [cri-o] clean up legacy deployments * disable cri-o per-distribution variables
2022-10-19 20:47:05 +08:00
- name: debian10
box: generic/debian10
cpus: 2
memory: 1024
groups:
- kube_control_plane
- kube_node
- k8s_cluster
project: upgrade test dependencies and drop ansible-core 2.11 (#10034) Molecule 5.0 require ansible-core 2.12.10. So this commit we update ansible-core from 2.12.5 to 2.12.10. We also drop supporting two ansible-core version. Also we now use the "oldest" still supported ansible-core version as both 2.11 is EOL and not supported by molecule. tests/molecule: remove linting in molecule to support molecule 5 tests/molecule: remove role name check for molecule 5 support Kubespray doesn't use ansible galaxy style naming so we have to disable that check. contrib/inventory_builder: fix tox.ini for tox4 tests/molecule: fix get_playbook in testinfra tests tests: upgrade most tests requirements Exclude ansible-lint for now, I will do that in a separate PR. tests/molecule: force kvm driver option If we don't do this it fallbacks to qemu emulated on our CI for some reasons. Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@proton.ch>
2023-06-03 11:40:40 +08:00
provider_options:
driver: kvm
Add CRI-O CI (#5460)
2020-04-22 21:09:52 +08:00
provisioner:
name: ansible
env:
ANSIBLE_ROLES_PATH: ../../../../
config_options:
defaults:
Replace callback_whitelist with callbacks_enabled (#8759) When running molecule jobs, we saw the folloing warning message: [DEPRECATION WARNING]: [defaults]callback_whitelist option, normalizing names to new standard, use callbacks_enabled instead. This feature will be removed from ansible-core in version 2.15. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg. callbacks_enabled has been added since Ansible 2.11 and Kubespray is using Ansible 2.12 at master branch. So we can use callbacks_enabled safely to avoid the warning message.
2022-06-10 04:15:45 +08:00
callbacks_enabled: profile_tasks
containerd: change default resolvconf_mode to host_resolvconf (#8247) * containerd: change default resolvconf_mode to host_resolvconf * Wait for kube-apiserver to come back after pod refresh * Handle resolv.conf gracefully * Retain currently configured DNS entries to ensure we don't break the resolvers * Suse uses wickedd for network management so no dhcp hooks * Molecule: increase ansible timeout * CI: Increase ansible timeout to 120s for Packet jobs
2021-12-10 06:09:06 +08:00
timeout: 120
Add CRI-O CI (#5460)
2020-04-22 21:09:52 +08:00
verifier:
name: testinfra