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.

326 lines
6.3 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
[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
[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
[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. .packet:
  3. extends: .testcases
  4. variables:
  5. ANSIBLE_TIMEOUT: "120"
  6. CI_PLATFORM: packet
  7. SSH_USER: kubespray
  8. tags:
  9. - packet
  10. except: [triggers]
  11. # CI template for PRs
  12. .packet_pr:
  13. only: [/^pr-.*$/]
  14. extends: .packet
  15. # CI template for periodic CI jobs
  16. # Enabled when PERIODIC_CI_ENABLED var is set
  17. .packet_periodic:
  18. only:
  19. variables:
  20. - $PERIODIC_CI_ENABLED
  21. allow_failure: true
  22. extends: .packet
  23. # The ubuntu20-calico-aio jobs are meant as early stages to prevent running the full CI if something is horribly broken
  24. packet_ubuntu20-calico-aio:
  25. stage: deploy-part1
  26. extends: .packet_pr
  27. when: on_success
  28. variables:
  29. RESET_CHECK: "true"
  30. packet_ubuntu20-calico-aio-ansible-2_11:
  31. stage: deploy-part1
  32. extends: .packet_periodic
  33. when: on_success
  34. variables:
  35. ANSIBLE_MAJOR_VERSION: "2.11"
  36. RESET_CHECK: "true"
  37. # ### PR JOBS PART2
  38. packet_ubuntu18-aio-docker:
  39. stage: deploy-part2
  40. extends: .packet_pr
  41. when: on_success
  42. packet_ubuntu20-aio-docker:
  43. stage: deploy-part2
  44. extends: .packet_pr
  45. when: on_success
  46. packet_ubuntu20-calico-aio-hardening:
  47. stage: deploy-part2
  48. extends: .packet_pr
  49. when: on_success
  50. packet_ubuntu18-calico-aio:
  51. stage: deploy-part2
  52. extends: .packet_pr
  53. when: on_success
  54. packet_ubuntu22-aio-docker:
  55. stage: deploy-part2
  56. extends: .packet_pr
  57. when: on_success
  58. packet_ubuntu22-calico-aio:
  59. stage: deploy-part2
  60. extends: .packet_pr
  61. when: on_success
  62. packet_centos7-flannel-addons-ha:
  63. extends: .packet_pr
  64. stage: deploy-part2
  65. when: on_success
  66. packet_almalinux8-crio:
  67. extends: .packet_pr
  68. stage: deploy-part2
  69. when: on_success
  70. packet_ubuntu18-crio:
  71. extends: .packet_pr
  72. stage: deploy-part2
  73. when: manual
  74. packet_fedora37-crio:
  75. extends: .packet_pr
  76. stage: deploy-part2
  77. when: manual
  78. packet_ubuntu16-flannel-ha:
  79. stage: deploy-part2
  80. extends: .packet_pr
  81. when: manual
  82. packet_debian10-cilium-svc-proxy:
  83. stage: deploy-part2
  84. extends: .packet_periodic
  85. when: on_success
  86. packet_debian10-calico:
  87. stage: deploy-part2
  88. extends: .packet_pr
  89. when: on_success
  90. packet_debian10-docker:
  91. stage: deploy-part2
  92. extends: .packet_pr
  93. when: on_success
  94. packet_debian11-calico:
  95. stage: deploy-part2
  96. extends: .packet_pr
  97. when: on_success
  98. packet_debian11-docker:
  99. stage: deploy-part2
  100. extends: .packet_pr
  101. when: on_success
  102. packet_centos7-calico-ha-once-localhost:
  103. stage: deploy-part2
  104. extends: .packet_pr
  105. when: on_success
  106. variables:
  107. # This will instruct Docker not to start over TLS.
  108. DOCKER_TLS_CERTDIR: ""
  109. services:
  110. - docker:19.03.9-dind
  111. packet_almalinux8-kube-ovn:
  112. stage: deploy-part2
  113. extends: .packet_periodic
  114. when: on_success
  115. packet_almalinux8-calico:
  116. stage: deploy-part2
  117. extends: .packet_pr
  118. when: on_success
  119. packet_rockylinux8-calico:
  120. stage: deploy-part2
  121. extends: .packet_pr
  122. when: on_success
  123. packet_rockylinux9-calico:
  124. stage: deploy-part2
  125. extends: .packet_pr
  126. when: on_success
  127. packet_rockylinux9-cilium:
  128. stage: deploy-part2
  129. extends: .packet_pr
  130. when: on_success
  131. variables:
  132. RESET_CHECK: "true"
  133. packet_almalinux8-docker:
  134. stage: deploy-part2
  135. extends: .packet_pr
  136. when: on_success
  137. packet_fedora38-docker-weave:
  138. stage: deploy-part2
  139. extends: .packet_pr
  140. when: on_success
  141. allow_failure: true
  142. packet_opensuse-docker-cilium:
  143. stage: deploy-part2
  144. extends: .packet_pr
  145. when: manual
  146. # ### MANUAL JOBS
  147. packet_ubuntu16-docker-weave-sep:
  148. stage: deploy-part2
  149. extends: .packet_pr
  150. when: manual
  151. packet_ubuntu18-cilium-sep:
  152. stage: deploy-special
  153. extends: .packet_pr
  154. when: manual
  155. packet_ubuntu18-flannel-ha:
  156. stage: deploy-part2
  157. extends: .packet_pr
  158. when: manual
  159. packet_ubuntu18-flannel-ha-once:
  160. stage: deploy-part2
  161. extends: .packet_pr
  162. when: manual
  163. # Calico HA eBPF
  164. packet_almalinux8-calico-ha-ebpf:
  165. stage: deploy-part2
  166. extends: .packet_pr
  167. when: manual
  168. packet_debian10-macvlan:
  169. stage: deploy-part2
  170. extends: .packet_pr
  171. when: manual
  172. packet_centos7-calico-ha:
  173. stage: deploy-part2
  174. extends: .packet_pr
  175. when: manual
  176. packet_centos7-multus-calico:
  177. stage: deploy-part2
  178. extends: .packet_pr
  179. when: manual
  180. packet_fedora38-docker-calico:
  181. stage: deploy-part2
  182. extends: .packet_periodic
  183. when: on_success
  184. variables:
  185. RESET_CHECK: "true"
  186. packet_fedora37-calico-selinux:
  187. stage: deploy-part2
  188. extends: .packet_periodic
  189. when: on_success
  190. packet_fedora37-calico-swap-selinux:
  191. stage: deploy-part2
  192. extends: .packet_pr
  193. when: manual
  194. packet_amazon-linux-2-aio:
  195. stage: deploy-part2
  196. extends: .packet_pr
  197. when: manual
  198. packet_almalinux8-calico-nodelocaldns-secondary:
  199. stage: deploy-part2
  200. extends: .packet_pr
  201. when: manual
  202. packet_fedora38-kube-ovn:
  203. stage: deploy-part2
  204. extends: .packet_periodic
  205. when: on_success
  206. packet_debian11-custom-cni:
  207. stage: deploy-part2
  208. extends: .packet_pr
  209. when: manual
  210. packet_debian11-kubelet-csr-approver:
  211. stage: deploy-part2
  212. extends: .packet_pr
  213. when: manual
  214. # ### PR JOBS PART3
  215. # Long jobs (45min+)
  216. packet_centos7-weave-upgrade-ha:
  217. stage: deploy-part3
  218. extends: .packet_periodic
  219. when: on_success
  220. variables:
  221. UPGRADE_TEST: basic
  222. packet_ubuntu20-calico-etcd-kubeadm-upgrade-ha:
  223. stage: deploy-part3
  224. extends: .packet_periodic
  225. when: on_success
  226. variables:
  227. UPGRADE_TEST: basic
  228. # Calico HA Wireguard
  229. packet_ubuntu20-calico-ha-wireguard:
  230. stage: deploy-part2
  231. extends: .packet_pr
  232. when: manual
  233. packet_debian11-calico-upgrade:
  234. stage: deploy-part3
  235. extends: .packet_pr
  236. when: on_success
  237. variables:
  238. UPGRADE_TEST: graceful
  239. packet_almalinux8-calico-remove-node:
  240. stage: deploy-part3
  241. extends: .packet_pr
  242. when: on_success
  243. variables:
  244. REMOVE_NODE_CHECK: "true"
  245. REMOVE_NODE_NAME: "instance-3"
  246. packet_ubuntu20-calico-etcd-kubeadm:
  247. stage: deploy-part3
  248. extends: .packet_pr
  249. when: on_success
  250. packet_debian11-calico-upgrade-once:
  251. stage: deploy-part3
  252. extends: .packet_periodic
  253. when: on_success
  254. variables:
  255. UPGRADE_TEST: graceful
  256. packet_ubuntu18-calico-ha-recover:
  257. stage: deploy-part3
  258. extends: .packet_periodic
  259. when: on_success
  260. variables:
  261. RECOVER_CONTROL_PLANE_TEST: "true"
  262. RECOVER_CONTROL_PLANE_TEST_GROUPS: "etcd[2:],kube_control_plane[1:]"
  263. packet_ubuntu18-calico-ha-recover-noquorum:
  264. stage: deploy-part3
  265. extends: .packet_periodic
  266. when: on_success
  267. variables:
  268. RECOVER_CONTROL_PLANE_TEST: "true"
  269. RECOVER_CONTROL_PLANE_TEST_GROUPS: "etcd[1:],kube_control_plane[1:]"