C12s/c12s-kubespray
3
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
c12s-kubespray/roles/container-engine/cri-o/molecule/default/molecule.yml

58 lines
1,018 B
YAML
Raw Normal View History

Add CRI-O CI (#5460)
2020-04-22 13:09:52 +00:00
---
driver:
name: vagrant
provider:
name: libvirt
Upgrade molecule to v3 (#6468) Signed-off-by: Victor Morales <v.morales@samsung.com>
2020-08-04 12:24:19 +00:00
lint: |
set -e
yamllint -c ../../../.yamllint .
Add CRI-O CI (#5460)
2020-04-22 13:09:52 +00:00
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 12:47:05 +00:00
- name: ubuntu20
[cri-o] molecule switch from ubuntu 18 to ubuntu 20
2022-05-03 19:56:33 +00:00
box: generic/ubuntu2004
Enable crio 1.18 (#6197)
2020-05-28 07:42:15 +00: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 00:26:05 +00: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 12:47:05 +00:00
- kube_node
- k8s_cluster
CI: Replace CentOS 8 with AlmaLinux 8 before CentOS 8 EOL end of 2021 (#8297)
2022-01-05 10:20:33 +00: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 08:18:07 +00: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 00:26:05 +00: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 12:47:05 +00:00
- kube_node
- k8s_cluster
Fix crio runc path on Ubuntu (#6035)
2020-04-28 12:28:06 +00:00
- name: fedora
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 12:47:05 +00:00
box: fedora/36-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 08:18:07 +00: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 00:26:05 +00: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 12:47:05 +00:00
- kube_node
- k8s_cluster
- name: debian10
box: generic/debian10
cpus: 2
memory: 1024
groups:
- kube_control_plane
- kube_node
- k8s_cluster
Add CRI-O CI (#5460)
2020-04-22 13:09:52 +00: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-09 20:15:45 +00: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-09 22:09:06 +00:00
timeout: 120
Add CRI-O CI (#5460)
2020-04-22 13:09:52 +00:00
lint:
name: ansible-lint
options:
c: ../../../.ansible-lint
verifier:
name: testinfra
lint:
name: flake8
Reference in a new issue Copy permalink