You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

72 lines
1.7 KiB

[2.22] Add hashes for kubernetes 1.26.11, 1.26.10 (#10704) * [kubernetes] Add hashes for kubernetes 1.26.11, 1.26.10 Make kubernetes 1.26.11 default * Workaround for yaml/pyyaml#601 * Convert exoscale tf provider to new version (#10646) This is untested. It passes terraform validate to un-broke the CI. * Update 0040-verify-settings.yml (#10699) remove embedded template * 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> --------- Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@proton.ch> Co-authored-by: piwinkler <9642809+piwinkler@users.noreply.github.com> Co-authored-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@proton.ch>
11 months ago
[2.22] Add hashes for kubernetes 1.26.11, 1.26.10 (#10704) * [kubernetes] Add hashes for kubernetes 1.26.11, 1.26.10 Make kubernetes 1.26.11 default * Workaround for yaml/pyyaml#601 * Convert exoscale tf provider to new version (#10646) This is untested. It passes terraform validate to un-broke the CI. * Update 0040-verify-settings.yml (#10699) remove embedded template * 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> --------- Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@proton.ch> Co-authored-by: piwinkler <9642809+piwinkler@users.noreply.github.com> Co-authored-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@proton.ch>
11 months ago
  1. ---
  2. .vagrant:
  3. extends: .testcases
  4. variables:
  5. CI_PLATFORM: "vagrant"
  6. SSH_USER: "vagrant"
  7. VAGRANT_DEFAULT_PROVIDER: "libvirt"
  8. KUBESPRAY_VAGRANT_CONFIG: tests/files/${CI_JOB_NAME}.rb
  9. tags: [c3.small.x86]
  10. only: [/^pr-.*$/]
  11. except: ['triggers']
  12. image: $PIPELINE_IMAGE
  13. services: []
  14. before_script:
  15. - apt-get update && apt-get install -y python3-pip
  16. - update-alternatives --install /usr/bin/python python /usr/bin/python3 10
  17. - python -m pip uninstall -y ansible ansible-base ansible-core
  18. - PIP_CONSTRAINT=tests/constraints.txt python -m pip install -r tests/requirements.txt
  19. - ./tests/scripts/vagrant_clean.sh
  20. script:
  21. - ./tests/scripts/testcases_run.sh
  22. after_script:
  23. - chronic ./tests/scripts/testcases_cleanup.sh
  24. allow_failure: true
  25. vagrant_ubuntu18-calico-dual-stack:
  26. stage: deploy-part2
  27. extends: .vagrant
  28. when: on_success
  29. vagrant_ubuntu18-flannel:
  30. stage: deploy-part2
  31. extends: .vagrant
  32. when: on_success
  33. vagrant_ubuntu18-weave-medium:
  34. stage: deploy-part2
  35. extends: .vagrant
  36. when: manual
  37. vagrant_ubuntu20-flannel:
  38. stage: deploy-part2
  39. extends: .vagrant
  40. when: on_success
  41. allow_failure: false
  42. vagrant_ubuntu20-flannel-collection:
  43. stage: deploy-part2
  44. extends: .vagrant
  45. when: on_success
  46. vagrant_ubuntu16-kube-router-sep:
  47. stage: deploy-part2
  48. extends: .vagrant
  49. when: manual
  50. # Service proxy test fails connectivity testing
  51. vagrant_ubuntu16-kube-router-svc-proxy:
  52. stage: deploy-part2
  53. extends: .vagrant
  54. when: manual
  55. vagrant_fedora37-kube-router:
  56. stage: deploy-part2
  57. extends: .vagrant
  58. when: on_success
  59. vagrant_centos7-kube-router:
  60. stage: deploy-part2
  61. extends: .vagrant
  62. when: manual